How to reset Internet Protocol (TCP/IP)

12/21/2011 1:47 PM

Article ID: 299357 - Last Review: September 23, 2011 - Revision: 11.0

How to reset Internet Protocol (TCP/IP)

System Tip This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the W indows 7 Solution Center

This article was previously published under Q299357

Introduction

One of the components of the Internet connection on your computer is a built-in set of instructions called TCP/IP. TCP/IP can sometimes become damaged or corrupted. If you cannot connect to the Internet and you have tried all other methods to resolve the problem, TCP/IP might be causing it. Because TCP/IP is a core component of Windows, you cannot remove it. However, you can reset TCP/IP to its original state by using the NetShell utility (netsh). This article describes two ways to reset TCP/IP. You must be logged on to the computer as an administrator. The first method uses a Fix it automated solution to reset TCP/IP. This method is designed for beginning to intermediate users. The second method describes how to use a command to reset TCP/IP manually. This method is designed for advanced users. To have us fix this problem for you, go to the Fix it for me section. If youd rather fix this problem yourself, go to the Let me fix it myself section.

Fix it for me

To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.

Fix this problem Microsoft Fix it 50199 Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows. Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem. Now go to the "Did this fix the problem?" section.

Let me fix it myself

Use a manual method to reset TCP/IP

Note This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, ask someone for help or contact Support. For information about how to contact Support, see the Microsoft Help and Support contact information Web site: http://support.microsoft.com/contactus (http://support.microsoft.com/contactus) The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually: 1. To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER: cmd 2. At the command prompt, copy and paste (or type) the following command and then press ENTER: netsh int ip reset c:\resetlog.txt Note If you do not want to specify a directory path for the log file, use the following command: netsh int ip reset resetlog.txt 3. Reboot the computer. 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\

netsh

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

How to reset Internet Protocol (TCP/IP)

12/21/2011 1:47 PM

To run the manual command successfully, you must specify a file name for the log, in which the actions that netsh takes will be recorded. When you run the manual command, TCP/IP is reset and the actions that were taken are recorded in the log file, known as resetlog.txt in this article. The first example, c:\resetlog.txt, creates a path where the log will reside. The second example, resetlog.txt, creates the log file in the current directory. In either case, if the specified log file already exists, the new log will be appended to the end of the existing file.

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base: 314067 (http://support.microsoft.com/kb/314067/ ) How to troubleshoot TCP/IP connectivity with Windows XP For more information, click the following article number to view the article in the Microsoft Knowledge Base: 811259 (http://support.microsoft.com/kb/811259/ ) How to determine and recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base: 314053 (http://support.microsoft.com/kb/314053/ ) TCP/IP and NBT configuration parameters for Windows XP

Sample Log File for NETSH INT IP RESET

The following is a sample of the log file that is generated by netsh when an IP reset command is issued. The actual log file might vary, depending on the configuration of the computer. When the TCP/IP registry keys have not been altered from their original configuration, there might be no actions logged in the file. reset SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\15\RegLocation old REG_MULTI_SZ = SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpDomain SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\DhcpDomain added SYSTEM\CurrentControlSet \Services\Netbt\Parameters\Interfaces\Tcpip_{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\NetbiosOptions added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{BAA9D128-54BB43F6-8922-313D537BE03E}\NetbiosOptions reset SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\NameServerList old REG_MULTI_SZ = 10.1.1.2 deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87ACB4E72693D10C}\AddressType added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces \{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\DefaultGatewayMetric added SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\DisableDynamicUpdate deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87ACB4E72693D10C}\DontAddDefaultGateway reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\EnableDhcp old REG_DWORD = 0 added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87ACB4E72693D10C}\NameServer added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces \{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\RawIpAllowedProtocols added SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\TcpAllowedPorts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87ACB4E72693D10C}\UdpAllowedPorts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces \{5B3675C3-6EB9-4936-B991-04DA31024C4E}\DisableDynamicUpdate reset SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\EnableDhcp old REG_DWORD = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces \{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAddress old REG_MULTI_SZ = 12.12.12.12 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936B991-04DA31024C4E}\IpAutoconfigurationAddress deleted SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationMask deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936B991-04DA31024C4E}\IpAutoconfigurationSeed reset SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\RawIpAllowedProtocols old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces \{5B3675C3-6EB9-4936-B991-04DA31024C4E}\SubnetMask old REG_MULTI_SZ = 255.255.255.0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936B991-04DA31024C4E}\TcpAllowedPorts old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services \Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\UdpAllowedPorts old REG_MULTI_SZ = 0 added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces \{BAA9D128-54BB-43F6-8922-313D537BE03E}\AddressType added SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\DefaultGatewayMetric added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB43F6-8922-313D537BE03E}\DisableDynamicUpdate deleted SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\DontAddDefaultGateway reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB43F6-8922-313D537BE03E}\EnableDhcp old REG_DWORD = 0 added SYSTEM\CurrentControlSet\Services \Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\NameServer added

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

How to reset Internet Protocol (TCP/IP)

12/21/2011 1:47 PM

\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\NameServer added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB43F6-8922-313D537BE03E}\RawIpAllowedProtocols added SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\TcpAllowedPorts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB43F6-8922-313D537BE03E}\UdpAllowedPorts reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\DefaultGateway old REG_MULTI_SZ = 10.1.1.2 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2BA3FE-3D246F90A81A}\DefaultGatewayMetric old REG_MULTI_SZ = 0 added SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\DisableDynamicUpdate reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2BA3FE-3D246F90A81A}\EnableDhcp old REG_DWORD = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\IpAddress old REG_MULTI_SZ = 10.1.1.1 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationAddress deleted SYSTEM\CurrentControlSet\Services \Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationMask deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2BA3FE-3D246F90A81A}\IpAutoconfigurationSeed reset SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\NameServer old REG_SZ = 10.1.1.2,10.1.1.3 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\RawIpAllowedProtocols old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2BA3FE-3D246F90A81A}\SubnetMask old REG_MULTI_SZ = 255.255.255.0 reset SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\TcpAllowedPorts old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\UdpAllowedPorts old REG_MULTI_SZ = 0 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList deleted SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\UseDomainNameDevolution <completed>Note In Windows Server 2003 Service Pack 1, you can use the netsh winsock reset command to repair Winsock.

Did this fix the problem?

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .

APPLIES TO
Keywords: kbmsifixme kbfixme kbhowto kbenv kbnetwork KB299357

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