16

Having got this problem and found this solution I think I should perhaps try netsh int ip reset reset command but I am afraid it can reset some important settings and disable me from reaching the server remotely. So what exactly does it reset?

2
  • 1
    Can someone address the issue of trying to run this remotely?
    – EricG
    Jan 4, 2014 at 15:57
  • 1
    @EricG: Assuming you mean how to reset after running the command how about this: netsh int ip reset && shutdown -r. Otherwise, please give more detail about the issue.
    – dunxd
    Mar 21, 2016 at 11:47

3 Answers 3

9

This is the first hit in google for the command you're asking about.

http://support.microsoft.com/kb/299357

When you run the reset command, it rewrites two registry keys that are used by TCP/IP. This has the same result as removing and reinstalling the protocol. The reset command rewrites the following two registry keys:

SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ 
SYSTEM\CurrentControlSet\Services\DHCP\Parameters\ 
0
8

It is shorthand for:

netsh int ip reset resetlog.txt

netsh i   i  r     r

The last 'r' being the "log file" that you really don't care to read.

What does it do? It hits your TCP/IP stack with a sledge hammer. And forcefully rebuilds it via a rewrite of two Registry keys:

SYSTEM\CurrentControlSet\Services\Tcpip\Parameters 
SYSTEM\CurrentControlSet\Services\DHCP\Parameters

This has the same effect as removing and reinstalling TCP/IP.

Please do this command in an Administrative command prompt http://www.thewindowsclub.com/how-to-run-command-prompt-as-an-administrator

See http://support.microsoft.com/kb/299357

5

I can tell you from experience that it removes any static IP information for all the NICs on the machine. I tried it on a server that was acting up and had to re-enter all the IP/netmask/gateway information for 6 network interfaces.

Interestingly enough, it did remember which interfaces were configured as static and what "items" were checked off on the interface (e.g. IPv4, Client for Microsoft Networks, etc). It also kept the interface names which we had previously changed.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .