Windows Forum

Ask something
Discussion Locked

STUMPED - network connectivity problem

0 helpful
16 replies

by lin

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a computer triple booting win98, NT4 wkstn, and NT4 svr. The Linksys nic card (brand new) is working properly since I am able to access the network and internet with win98. Both NT operating systems are unable to get an ip address. When I type ipconfig, I get the message "Windows NT IP Configuration" and nothing else (ipconfig /all will list only the host name, dns servers,...,NetBIOS Resolution Uses DNS -- nothing about the network adapter). Pinging 127.0.0.1 works. The same thing happens if using DHCP or static addresses. The networking services are installed properly since I can see network neighborhood, microsoft windows network, and the workgroup - absolutely nothing else. The workgroup is the same on all systems (98,NT,ME). Event viewer has a message that the adapter service failed to start because "A device attached to the system is not functioning" (event ID 7000). All ports on the switch and all cables were tested and are ok. I've already tried reinstalling NT operating systems, uninstall & reinstall all network services, protocols, and drivers.
What am I missing? Why is NT unable get an ip address?

16 replies

by geppetto

Lin,

The way that you describe your problem only indicate one thing to me. There is a possibility that the NT driver for the Linksys adapter is not working properly. Try to see if you can download a newer driver from vendor's web site.

by sfo farmer

I'd agree with #1 on replacing the driver, (especialy the NT4 driver) but I would also look at the BIOS and IRQ's to see if you have a hardware conflict that NT4's plug and play may not address. Also what are you getting the DHCP address from? If you can ping the loopback- that means the adapter seems to be working... Double check your config to make sure the netmask is good. The only time I've seen this on a server I had to (do what you did) reinstalled the TCP/IP protocol... Last question- have you re applied the service pack? Try it. G'luck!

by mike_fry

I agree with the other guys... The driver is no good. Make sure you are using the driver that came with the nic (not the one NT detects from its own files) or download a driver from the web.
Remember that NT is 4-5 years old now and that the drivers it supplies are a little out-dated...

by bill cassada

You have to keep in mind that NT is not Plug and Play....sometimes the interrupts will not be assigned as you had hoped (or as the driver expects). Make sure your interrupt is not conflicting with another device (use NT DIAGNOSTICS under ADMIN TOOLS to check this). You may have to update the driver. I would also recommend hitting the Linksys website and see what they have to say. If you can't resolve the problem let us know.

by Former member

I think your TCP/IP properties are corrupted, not the NIC drivers. Could be that your TWO NT OSes have corrupted each other...possibly. Having two NT OSes on one box is tricky. Reapply the service pack and trya again..

by Former member

Oh, just read something in your post that may indicate NIC problems, try the above suggestions and then try mine if they don't work. Good luck..

by rmiller

NT doesn't support PNP make sure your BIOS is set for a NON-PNP OS (The M'board will then handle the PNP config instead of the OS)Then check properties in Network Neighborhood and make sure the NIC is installed.

This discussion is closed to new replies.