Network issue

[RTSDaddy2]

Ok

I have one PC up and running on the internet at school. You would think networking would be a piece of cake, but true to form, I've hit a road block....at least I think.

The comps are all running Windows XP Home edition. The one that is working has IP address of 192.168.1.65, subnet is 255.255.255.0, Default of 192.168.1.254.

I cannot get the other machines to connect. I try to set up a new connection, I get a message telling me it can't find the network hardware. I have no 1394 visible, no LAN icon visible, nothing.  I KNOW I'm not seeing the forest for the trees here....would it work to go to the second computer and put in a similar IP?

Been at this for over two hours - really frustrated, because again I KNOW I've missed the simple fix

[newmanfamilyvlogs]

if you're not seeing an adapter in the device manager it won't matter if you've set an IP address anywhere. You need to verify that the network adapter is working first.

It would also probably make your job easier in the future to get some cheap router that can run a DHCP server instead of setting static IPs on any machines.

[RTSDaddy2]

COM port is up and running but Ethernet controller driver is not installed.  Is that the problem? If so, how do I reinstall the driver without a windows XP disc (waitaminute...not sure you should answer that).

We're not doing static addresses as such - it SHOULD be a straight ethernet to router / modem hookup...but it's not working.

[newmanfamilyvlogs]

COM port should have nothing to do with this.

To re-install the driver (you do not need an XP disk and there is nothing illegal about that) you'll first need to know what ethernet controller we're talking about. Locate it in your device manager (it will likely have a yellow 'yield' logo on it since there is no driver installed), look at it's properties, go to the "Details" tab then pick "Hardware Ids". The VEN_xxxx&DEV_xxxx part of it (where xxxx is some hexadecimal string) will tell us exactly what network device it is so we can locate drivers for it.

[RTSDaddy2]

PCI\VEN_8086&DEV_1229&SUBSYS_002E1028&REV10
PCI\VEN_8086&DEV_1229&SUBSYS_002E1028
PCI\VEN_8086&DEV_1229&CC_020000
PCI\VEN_8086&DEV_1229&CC0200

You mean that tells me something?   Good god man, I'm glad YOU know what it says!

[newmanfamilyvlogs]

Means you need these drivers:
http://www.intel.com/support/network/sb/cs-006103.htm

[gryhnd]

You've found the answer I see, but I ran into the same problem today with a Vista reinstall.

Basically it's this: chances are your hardware is more recent than the Windows install disks you have. So unless you slipstream in your own drivers to your own custom install, this is pretty common.

Much like why we have to download video drivers to get away from the stock 800x600 8bit color

Vista (pre SP1) could see and ID the Realtek onboard LAN but couldn't do a damn thing about it. I put the driver from MSI (my MB mfg) on a flash drive and installed it that way. Poof...up and running.

[RTSDaddy2]

I would have never figured that out without your help. Thanks for the info!

[newmanfamilyvlogs]

Im guessing very few of you share my appreciation for the humor in Intel's vendor ID being 8086.

[nick3092]

Sadly, I do.  I've had to hunt down drivers using this method more than I care.  Mainly when working on some custom cheaply built PC for someone.

[RTSDaddy2]

Thank you boys! Every computer that is running in my lab now also has internet access!

[newmanfamilyvlogs]

Glad to help!

[Mikezilla]

Good ol cotmm and his genius!