TCP/IP doesn't initialize properly on boot

[Swany]

This is a weird one. I have a Windows XP installation with an HP 100Mbit ethernet adapter.

When windows boots up, it does not assign the ip address that I have manually configured to the card. Instead, it assigned 0.0.0.0

If I view the status of the card, it says the IP address is "misconfigured."

However, I can get the IP to assign to the card one of two ways. It will fix itself if I stop and restart the card through device manager. I can also open the connection properties, uncheck TCP/IP click ok, open it back up and recheck TCP/IP. After I do either of the above, my ip address is assigned and everything works fine.

I wonder if anyone else has this problem with any other network adapters. Two completely different XP installs on this machine have had the same problem with this card, and I know the card is good (it works fine in 98, 2k, linux), so I am assuming it is an XP driver issue.

Any thoughts? .
.. Eat, think and be merry .
... ....................... .

 

[rjkrash]

It sounds like the card is losing it's configuration completly and XP is seeing it at startup and assigning default setttings.

Sounds like a driver or firmware problem. What is the model of your NIC? Have you checked with HP's site for updated software for XP.

Maybe the card has a 'turn off to conserve power' option. Some NICs do. Check to see if there is such an option from the Advanced tab of the NIC's properties (from System Properties > Hardware > Device Manager right click on the NIC icon and choose Properties > Advanced) and if so disable it.


The two rules for success are:
1. Never tell them everything you know.