Scott Hanselman

browse by category or date

The Nuclear Option: Resetting The Crap Out Of Your Network Adapters in Vista

September 20, '07 Comments [7] Posted in Musings
Sponsored By

I was having a number of strange network issues on a laptop today. Here's the complete nuclear option for resetting your whole IP stack. This is for when "Diagnose and Repair" isn't cutting it. Thanks to JohnP for his help.

  • Go to the Start Menu, type cmd and right click, and select "Run As Administrator"
  • Type the following commands, each followed by pressing enter.
    • ipconfig /flushdns
    • nbtstat -R
    • nbtstat -RR
    • netsh int reset all
    • netsh int ip reset
    • netsh winsock reset

UPDATE: On Windows 7, you'll need to do this to reset your network adapters:

  • ipconfig /flushdns
  • nbtstat -R
  • nbtstat -RR
  • netsh int reset all
  • netsh int ipv4 reset
  • netsh int ipv6 reset
  • netsh winsock reset

Now, reboot and pray. Possibly not in that order.

« The Mystery of the Failed Live Meeting L... | Blog Home | Managing Multiple Configuration File Env... »

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Comments [7]
Thursday, September 20, 2007 10:56:09 PM UTC
Another command to resolve Vista networking issues. I had to do this in order for TortoiseSVN to work through SSH.

netsh interface tcp set global autotuninglevel=disabled
Alan Le
Thursday, September 20, 2007 11:07:12 PM UTC
After typing cmd you can hold Ctrl + Shift and hit Enter to run as Administrator, its way quicker!
Fabio Gomes
Friday, September 21, 2007 3:34:59 AM UTC
I seems like your problem is the use of Vista. Perhaps you should downgrade to a more stable OS.
Eddie
Friday, September 21, 2007 6:17:32 AM UTC
Great! Thanks!

Why is it we can't trust Windows to actually repair anything? Repairing software almost never solves the issue, and neigher does repairing a network connection.

Andrew
Friday, September 21, 2007 9:40:18 AM UTC
I have had recent difficulties on XP and Vista with network access. Both times I found that the Microsoft TCP/IP version 6 protocol was installed on the network interface. After unistalling, my network connection began working again. Not sure if its Microsofts TCP/IPv6, or just my older MS Wireless Router having an issue with TCP/IPv6? Also, I don't remember installing TCP/IPv6 -- maybe Windows Update?
J. Joseph
Friday, September 21, 2007 3:10:30 PM UTC
I've found that this happens with great frequency on two of my three Vista machines. I keep a shortcut to Control Panel\Network Connections on my desktop, and actually have to just click on the net adapter having issues, click "Disable", wait about 10 seconds (the waiting is key, alas), then click "Enable". This fixes the issue almost every time (about 1 in 10 times I do need to reboot as well).

All in all, yes, I think the IPv6 stack needs some additional debugging. Having written a custom TCP/IP stack, I completely sympathize with the proto stack dev team at MS. IP is a foobugly protocol to implement.

Cheers,
Mike
Mike Henderson
Sunday, September 23, 2007 1:25:40 PM UTC
Thanks!

I just had to reboot because of Network issues... I Did remember reading this, but after the Network was down, I had some issues reaching this resource ;)

I made a small batch file so I can try it the next time it happens (And it happens quite regulary)
Heiko Hatzfeld
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.