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 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.


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.

Restart your PC into Safe Mode with Networking.

Edit your registry. Delete the following keys:-

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.


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


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.




42 thoughts on “Trashed tcp on your nic?

  1. 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.

  2. I spent 20 hours trying to fix this and 2 almost sleepless nights. I have also been battling it off and on for over 6 months on my tecra S2 laptop from Toshiba. This fixed it up immediately. I also uninstalled XP SP@ and my Cisco VPN client which I noticed were both causing occasional network problems.

    Thanks again

  3. Got the same error message ("Failed to query TCP/IP settings") but it was after I’ve installed Forti Client that was incompatible with my anti-virus software.

    I did a system restore and it worked.


    1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click System Restore

    2. Click Restore my computer to an earlier time, and then click Next.

    I found it out from Microsoft support:;EN-US;Q286562&ID=KB;EN-US;Q286562&

    Can be useful to some people.

  4. I had precisely this “Failed to query TCP/IP” error on a notebook. Couldn’t do a system restore because the user had already been monkeying with it for months.

    Uninstalling and reinstalling TCP/IP per these instructions did the trick!!

    Thank you, my New Year’s Day holiday can now be resumed!

  5. Tried the above and it did allow me to uninstall TCP/IP – Neat trick!
    But overall this didn’t fix the problem.

    Turned out putting a different network card fixed the issue. (NEC worked, Davicom didn’t!)

    Get a decent network card – The Davicom is now in the bin.


  6. Hi…
    I tried the registry changes mentioned above, to no avail. I restored to an earlier date, twice, to no avail. Been trying to fix the “failed to query TCP/IP” error off and on for over a week, maybe two. Finally, on a hunch I’d had since the start, I uninstalled about 8 Windows XP updates that installed automatically around the time I lost my internet connection, and LO AND BEHOLD, I had my tcp/ip back! I didn’t do the uninstall one at a time, so I don’t know which one it was, but here are the numbers: KB916281, KB914389, KB917953, KB917344, KB917734, KB911280, KB918439
    Pass it on, Microsoft screws us again!!!

  7. I had a user with a “network problem”.  When I went to his PC and tried an ipconfig /all – nothing would be listed except “Windows IP Configuration” – no adapters or anything else listed.   I tried repairing a network connection and got the “Failed to query TCP/IP settings” mentioned above.  I was quite surprised that TCP/IP couldn’t be uninstalled/re-installed natively.  The steps listed above allowed me to do this and fixed my problem.  What caused the problem is unknown but the user did state that it seemed to start happening after he unistalled a Beta version of Visual Studio .NET.

  8. Before trying that lengthy fix.  Try the simple solution at this URL:

    It says, “…all I did was go into the Properties for the Local Area Connection and untick TCP/IP…click OK and then go back in and tick TCP/IP again. This must reset the settings for the TCP/IP protocol on that network interface.”.

    I tried that and it worked for me!

  9. I tried this and sure enough, I’m up and running again.  Big thanks.  Now I just need to get rid of the new second copy of XP that I installed before finding this.

  10. I worked on two computer in the past two weeks with the same problem. I stumbled on your solution for the first computer and it worked great. Unfortunately I did not bookmark your site and spent a couple days using other solutions I found on the net–resetting TCP/IP or restacking it. Nothing worked. I finally found your site again when I did a google search on “nettcpip”. Followed your instructions and it worked like a charm! I cant understand why this isnt a standard solution or one offered by Microsoft support.

    Thank you so much. Your site is bookmarked now. 🙂

  11. You guys Rock! I’ve been batteling for several days now off and on after ghosting to a new hard drive to fix the tcp/ip bug that disables the netcard, and this fix worked. Microsoft themselves are unaware how to fix this error as far as I can see.

  12. The tip from ubiquity worked for me:

    “go into the Properties for the Local Area Connection and untick TCP/IP…click OK and then go back in and tick TCP/IP again. ”

    You must reboot for the changes to take full effect.

    The problem occurred after installing drivers for a $20 USB camera purchased at a local drug store. Be careful what you install on your machine!

  13. I was having the 169.254.x.x/ able to renew, etc, etc issue.  The tricks listed here didn’t work at all.  I’m sure the inf files were bad.  What worked was 1) copying onto disk the inf folder from the desktop pc that is able to  connect to the net with no problem 2) deleting the Winsock and Winsock2 from the registry 3) deleting the inf folder from the non-internet laptop 4) copying the inf folder from disk to the laptop 5) went into the connection I wanted to fix 6) clicked on Properties and then Install 7) clicked on Protocol, then Have Disk, then typed c:\Windows\inf 8) restarted the computer.  Somewhere along the line, doing that disabled the IPv6 Windows Firewall Driver…even though I had the Windows Firewall set to off.  I used ipconfig /all just to verify and lo and behold…success!!!  Finally!!  I had read on another site about someone who just replaced a couple files and registry keys, but I figured replacing the whole folder couldn’t hurt since they were both XP.  What doesn’t matter with this fix is whether one is XP Pro and one is XP Home…at least that I can tell.  In case I’m wrong, I took the inf folder from Home pc to Pro laptop.

  14. I cannot get tcpip to uninstall. I have tried all of the above instructions with no avail. I am unable to run restore. 24 hrs of head scratching and eyes burning. I have replaced the nic Any other hints would be apprectiated.

  15. I have tried all of the above with no joy. I’m going to install another hard drive so I can retrieve email etc. and start over.


  16. Reinstalling TCP/IP as per the directions did indeed revive my ability to connect to the net.

    I usually have a backup copy of my C: disk so that in cases of disastrous failures I can reinstall. In this case the older version worked until some updates were installed and the problem returned. On that copy reverting to a restore point a day earlier solved the problem.

    I then reinstalled the originally failed copy of C: – only to find there were no restore points on it – so I reinstalled TCP/IP and that solved the problem on that copy.

    It really appears that MS update was the culprit in both cases.


  17. When I tried reinstalling the tcp/ip on the system, I get the following error: “Could not add the requested component. the error is: an extended error has occurred.” Any clue how to get around this?

  18. I also had encountered this problem on my mom’s laptop.  I think it was due to a virus corrupted some network files.  I’m not sure but I did a restore and it’s back up.  Thanks

  19. You’r the real man . . . You’r great solution work for me . . . You’r the best . . . .[ I’m so (edited) happy ]

  20. Dude, thanx a lot for putting on web. I wasted a night and a day getting my internet up and running. It got fixed after i followed the steps mentioned on this post.


    Tony – The “M E T A L H E A D”

  21. Fabulous!  I had my doubts, but it worked.  Thank you so much, I know you just saved me a ton of time!  FYI, I tried the comments from ‘ubiquity’, ‘Jerry’ and ‘Justin’ first because they looked easier….nothing.  But the original post worked like a charm.

  22. Stuart – THANKS A MILLION

    I tried a ton of sites and tips to no avail.  

    This stopped DHCP Service was an awesome symptom description!

    Some spyware/virus replaced the tcpip.sys file in the

    system32\drivers and the system32\dllcache folder.

    Thanks to you and the link that you provided, everything is back to normal!!!

  23. Tried the original solution and it did allow me to uninstall TCP/IP – Pretty cool.

    netsh int ip reset resetlog.txt

    netsh winsock reset

    But overall this didn’t fix the problem.

    I knew that the problem was related to one of the Security Updates for Windows XP.

    I identified Security Update for Windows XP (KB917953) as the culprit.

    Use Windows Explorer to navigate to the C:Windows “$NtUninstallKB917953$” folder and use the uninstall utility in the folder.

    Note:  I noticed two other folders related:

    “$NtUninstallKB917953$(2)”  and


    I did not have to do anything using those in order to fix the problem.

  24. Spent about a day fighting this one until I found this post. Original susgestion worked after trying all the easy stuff.

  25. Unticking and reticking TCP/IP did not work. Before trying the harder stuff, I uninstalled Windows XP SP3. That fixed it. Originally, SP3 gave me an MSWSOCK.DLL error. Trying to fix that, I got the QUERY TCP/IP error. SP3 is incompatible with the SiS 900 PCI Fast Ethernet Adapter on my MB or my Linksys WRT150N wireless-n router.

  26. I only have to say… Thank You!!!, Thank You!!!, Thank You!!!, So much…

    After too much Googling finally a real solution… My wireless adapter was only working with fixed IP address since a virus changed the DNS and my computer has never the same. The command “netsh int ip reset” does not help so much in most of the cases.

  27. Thanks! The original directions, plus replacing the tcpip.sys with a copy from an XP machine (both XP Pro, SP2) with healthy networking, restored TCP/IP to sanity. The netsh commands mentioned in the original directions and comments may also have had a hand in the fix. I tried those after following the procedure but before replacing tcpip.sys. Extra thanks to Stuart for the final piece of the puzzle!

  28. Thank you for this tip!
    I broke the VPN client due to a malfunctioned wireless network adapter, and each time I tried to connect Windows cut off the connection saying that some hardware was not functioning.
    With your guidance, I reconnected the VPN again.
    Thanks a lot!

  29. My loss of internet connectivty was caused by a rootkit
    removal tool quarantining my c:\windows\system32 file
    called ipsec.sys. If you don’t have that file in that folder
    you’ll experience all the same symptoms as the above
    users point out. Hope this helps!
    forums rock!

  30. I followed the instructions and it worked great for me. Didnt neet to do the netsh ip reset, just the inf file change, install, uninstal, and install on the affected adapter.

    Did the reboots, and now ipconfig shows my wireless adapter and it connects properly.

    Thanks thanks thanks thanks for providing this. I spent hours trying to sort this out, I knew it was a binding issue, but just couldnt see where in the registry.

Leave a Reply

Your email address will not be published. Required fields are marked *