Trashed tcp on your nic?
Have you suffered a slow xp start and no working nic? Ipconfig will not work? Have you ever suffered a nic that would not repair in XP? You get errors suggesting that it cannot see the tcp. I started disabling antivirus services with no joy. I found this comment at http://www.bangsar.net/mt-archives/000279.html His comment lets you uninstall the tcp so that you can do a fresh install of the tcp.
Note that this did not solve my problem but it is sort of neat that you can yank out the tcp with an edit of the nettcpip.inf.
Quote:
Problem:
Can't connect to the network. Your connection says you are connected, but no packets go through at all. Your connection's "Connection Status" info does not show anything about your IP address. Clicking on Repair gives you "Failed to query TCP/IP settings" or something like that.
Solution:
Restart your PC into Safe Mode with Networking.
Edit your registry. Delete the following keys:-
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Winsock
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Winsock2
Open the nettcpip.inf file in your %winroot%/inf folder (%winroot% is usually c:/windows).
Find the [MS_TCPIP.PrimaryInstall] section. Change the Characteristics value from 0xA0 to 0x80.
Open the properties of the network connection you want to fix. In the General tab, click on the Install button. Click on the Have Disk button, and point the location to %winroot%/inf. After that select TCP/IP (not version 6).
Now you would notice that you can uninstall TCP/IP! Do that, then restart the PC.
Go back to your network connection, and install TCP/IP again as per the above. After another reboot, you should be up and running.
Endquote
Personally I could not get this to work last time I tried on XP. I hope you have better luck. I also noted that the XP network repair tool may yank out the ISA 2004 firewall client stuff. Just run the firewall clinet repair or install it again to fix that problem after you did your reboot.
I suffered a server that refused to startdhcp, dns and wins. I beat on the server a long time remove phantom nics, reboots and even a full restore. On that server I exported the winsock and winsock2 keys from the registry. I deleted those keys. I rebooted the server. I imported those keys. I rebooted the server and all was well. Pretty goofy but it worked and I had nothing to lose. Your mileage may vary and you better have good backup of the whole server before you do this kind of crazy stuff.
Note from DJ
Quote
This along with a TCP/IP reset using the netsh command:
netsh int ip reset resetlog.txt
Did the trick for me...
This happens to my system frequently and usually a system restore from a checkpoint from the previous night fixes it. This time not.
endquote