Running netsh int ip reset c:\resetlog on a WINDOWS 2000 OS

[KodeBlack]

Here's a puzzler.......

"netsh int ip reset c:\resetlog.txt" resets the tcp/ip on a Windows XP machine, obviously..... The question is, does it do the same for a Windows 2000 machine? I recently ran into someone getting RAS error 678 on a Windows 2k machine and I ran this command on her machine, black box appeared and disappeared, we rebooted the system and recreated the DUN, had try to dial, connected! Page was visible and everything. She had called 6 different techs before I did this to her machine, the very first of which had gone through cmd to reset tcp/ip, rebooted, and rebuilt the dun. Still after that, she had gotten 678 until she got to me..... Does the netsh command actually work on Windows 2000?

 

[bcastner]

Netsh int ip reset filename is a formally documented XP Netsh.exe syntax. It is shorthand to the scripting portion of neths.exe for: interface IP reset logfile

For Windows 2000, passing the script command: "interface reset" is vaguely documented. Probably because it does a poor job of things. The scripting engine in netsh.exe likely ignores the logfilename, and the IP context value. So you get the end result of netsh interface reset.

. the formal way to do this repair in Win2k is by hand:

http://support.microsoft.com/default.aspx?scid=kb;en-us;318584

. See faq7779-4625 for a utility that does this easily for you in Windows versions 9x, ME, Win2k and XP; including replacing a corrupted Winsock and Winsock2 registry stack with clean entries suitable for Win2k.

As discussed in the FAQ, the issue of corruption in the Winsock service stack is quite common. Corruption in the service entries for TCP/IP are not quite as common, but common enough.

If you have issues you believe are due to Winsock corruption, download and use WinsockFix. If still no joy, follow the second half of the MS KB article about restoring TCP/IP and DUN service entries, essentially what you ended up doing in your description above.

But a thorough job of it is very worthwhile. Consider too the possibility of malware. See faq608-4650 for suggestions as to detetection and malware removal.

An interesting feature of XP with Service Pack 2 is not only was the Winsock stack given a netsh.exe repair command of its very own, but the Winsock stack is "self-healing", in that it will attempt to block and/or remove entries that seem inappropriate.

Best wishes,
Bill Castner