Thursday, August 13, 2009

How to reset TCP/IP protocol if it becomes corrupted

How to reset Internet Protocol (TCP/IP)

View products that this article applies to.

This article was previously published under Q299357

Introduction
One of the components of the Internet connection on your computer is a built-in...

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 you'd rather fix this problem yourself, go to the "Let me fix it myself" section.

Back to the top

Fix it for me
To fix this problem automatically, click the Fix this problem link. Then click R...

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.

Back to the top

Let me fix it myself
Use a manual method to reset TCP/IP Note This section is intended for advanced c...

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:

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

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.

Back to the top

More Information
For more information, click the following article number to view the article in...

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

Back to the top

REFERENCES
For more information, click the following article number to view the article in...

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-54BB-43F6-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-87AC-B4E72693D10C}\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-87AC-B4E72693D10C}\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-87AC-B4E72693D10C}\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-87AC-B4E72693D10C}\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-4936-B991-04DA31024C4E}\IpAutoconfigurationAddress deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationMask deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-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-4936-B991-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-54BB-43F6-8922-313D537BE03E}\DisableDynamicUpdate deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\DontAddDefaultGateway reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\EnableDhcp             old REG_DWORD = 0  added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\NameServer added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\RawIpAllowedProtocols added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\TcpAllowedPorts added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-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-4E2B-A3FE-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-4E2B-A3FE-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\{BD2859BA-B26A-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-4E2B-A3FE-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\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\RawIpAllowedProtocols             old REG_MULTI_SZ =                 0  reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-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\{BD2859BA-B26A-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.

Back to the top

Did this fix the problem?
Check whether the problem is fixed. If the problem is fixed, you are finished wi...

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

Back to the top

APPLIES TO

Microsoft Windows XP Professional
Microsoft Windows XP Home Edition
Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
Microsoft Windows Server 2003 R2 Datacenter x64 Edition
Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
Microsoft Windows Server 2003 R2 Enterprise x64 Edition
Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
Microsoft Windows Server 2003 R2 Standard x64 Edition
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows Server 2003, Datacenter x64 Edition
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Standard x64 Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Windows Server 2008 Datacenter without Hyper-V
Windows Server 2008 Enterprise without Hyper-V
Windows Server 2008 for Itanium-Based Systems
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Datacenter without Hyper-V
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Enterprise without Hyper-V
Windows Server 2008 R2 Standard
Windows Server 2008 R2 Standard without Hyper-V
Windows Server 2008 Service Pack 2
Windows Server 2008 Standard without Hyper-V
Windows Server 2008 Datacenter
Windows Server 2008 Enterprise
Windows Server 2008 Standard
Windows Vista Enterprise 64-bit Edition
Windows Vista Home Basic 64-bit Edition
Windows Vista Home Premium 64-bit Edition
Windows Vista Ultimate 64-bit Edition
Windows Vista Business
Windows Vista Enterprise
Windows Vista Home Basic
Windows Vista Starter
Windows Vista Ultimate

Get Clipmarks - The easiest way to email text, images and videos you find on the web.

If it ever happened to you

clipped from support.microsoft.com

How to determine and to recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista

When you try to release and renew the IP address by using the Ipconfig program (Ipconfig.exe), you may receive one of the following error messages.
Message 1

An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.

Message 2

An error occurred while renewing interface Local Area Connection: the requested service provider could not be loaded or initialized.

When you start Internet Explorer, you may receive the following error message:

The page cannot be displayed

When you use your computer, you may receive the following error message:

Initialization function INITHELPERDLL in IPMONTR.DLL failed to start with error code 10107

Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.

When you use the ipconfig /renew command, you may receive the following error messages.

Message 1

An error occurred while renewing interface local area connection: an operation was attempted on something that is not a socket. Unable to contact driver Error code 2.

Message 2

The operation failed since no adapter is in the state permissible for this operation.

Message 3

The attempted operation is not supported for the type of object referenced.

In Device Manager, when you click Show Hidden Devices, the TCP/IP Protocol Driver is listed as disabled under Non-Plug and Play drivers, and you receive error code 24.

When you create a dial-up connection, you may receive the following error message:

Error 720: No PPP Control Protocols Configured

Back to the top

CAUSE
These issues may occur if the Winsock registry keys are damaged or corrupted. Ma...

These issues may occur if the Winsock registry keys are damaged or corrupted.

Back to the top

Manual steps to determine whether the Winsock2 key is corrupted for Windows XP users

To determine if the symptoms are caused by a problem with the Winsock2 key,use one of the following methods.

Method 1: Use the Netdiag tool

To use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps.

Notes

If you already have Support Tools installed, go to the second procedure in this section.
If you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2.

Insert your Windows XP Setup CD, and then locate the Support\Tools folder.
Double-click the Setup.exe file.
Follow the steps on the screen until you reach the Select An Installation Type screen.
On the Select An Installation Type screen, click Complete, and then click Next.

When the installation is complete, follow these steps:

Click Start, click Run, type Command, and then click OK.
Type netdiag /test:winsock, and then press ENTER.

The Netdiag tool will return the test results for several network components, including the Winsock. For more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v

Method 2: Use the Msinfo32 program

Note Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.

Click Start, click Run, type Msinfo32, and then click OK.
Expand Components, expand Network, and then click Protocol.
You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
- MSAFD Tcpip [TCP/IP]
- MSAFD Tcpip [UDP/IP]
- RSVP UDP Service Provider
- RSVP TCP Service Provider
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed.

If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.

If there are more than ten sections in the list, you have third-party additions installed.

If there are fewer than ten sections, there is information missing.

Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:

MSAFD nwlnkipx [IPX]

Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.

If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.

To have us reset the Winsock settings for you, go to the "Fix it for me" section. To reset the Winsock settings yourself, go to the "Let me fix it myself" section.

Back to the top

Fix it for me
To reset the Winsock settings automatically, click the Fix it button or link. C...

To reset the Winsock settings automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Fix this problem
Microsoft Fix it 50203

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, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Next, go to the "Did this fix the problem?" section.

Back to the top

RESOLUTION
Manual steps to recover from Winsock2 corruption Windows XP with Service Pack 2...

Manual steps to recover from Winsock2 corruption

Windows XP with Service Pack 2 instructions

To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed, type netsh winsock reset at the command prompt, and then press ENTER.

Note Restart the computer after you run this command. Additionally, for computers that are running Windows XP SP2, there is a new netsh command that can rebuild the Winsock key. For more information, visit the following Web site:

http://technet.microsoft.com/en-us/library/bb457156.aspx (http://technet.microsoft.com/en-us/library/bb457156.aspx)

Warning Programs that access or monitor the Internet such as antivirus, firewall, or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.

Note If these steps do not resolve the problem, follow the steps in the next section.

Windows XP without Service Pack 2 instructions

To repair Winsock if you do not have Windows XP SP2 installed, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.

Step 1: Delete the corrupted registry keys

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

For more information about how to back up the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows XP and Windows Vista

Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
When you are prompted to confirm the deletion, click Yes.

Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.

Step 2: Install TCP/IP

Right-click the network connection, and then click Properties.
Click Install.
Click Protocol, and then click Add.
Click Have Disk.
Type C:\Windows\inf, and then click OK.
On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.

If Internet Protocol (TCP/IP) does not appear, follow these steps:
1. Click Start, and then click Search.
2. In the Search Companion pane, click More advanced options.
3. Click to select the following three check boxes:
  - Search system folders
  - Search hidden files and folders
  - Search subfolders
4. In the All or part of the file name box, type nettcpip.inf, and then click Search.
5. In the results pane, right-click Nettcpip.inf, and then click Install.
Restart the computer.

Back to the top

Manual steps to determine whether the Winsock2 key is corrupted for Windows Vista users

Click Start, click Run, type Msinfo32, and then click OK.
Expand Components, expand Network, and then click Protocol.
Ten sections appear under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
- MSAFD Tcpip [TCP/IP]
- MSAFD Tcpip [UDP/IP]
- MSAFD Tcpip [TCP/IPv6]
- MSAFD Tcpip [UDP/IPv6]
- RSVP UDP Service Provider
- RSVP TCP Service Provider
- RSVP UDPv6 Service Provider
- RSVP TCPv6 Service Provider
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on such as proxy software installed.

If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.

If there are more than ten sections in the list, you have third-party additions installed.

If there are fewer than ten sections, there is information missing.

MSAFD nwlnkipx [IPX]

Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.

If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.

Back to the top

Manual steps to recover from Winsock2 corruption for Windows Vista users

Winsock corruption can cause connectivity problems. To resolve this issue by using Network Diagnostics in Windows Vista, follow these steps:

Click ,
Collapse this imageExpand this image
and then click Network.
Click Network and Sharing Center.
In the Network and Sharing Center box, click Diagnose and Repair.

Note You may also access the Network and Sharing Center in Control Panel.

Reset Winsock for Windows Vista

To reset Winsock for Windows Vista, follow these steps:

Click
Collapse this imageExpand this image
, type cmd in the Start Search box, right-click cmd.exe, click Run as administrator, and then press Continue.
Type netsh winsock reset at the command prompt, and then press ENTER.

Note If the command is typed incorrectly, you will receive an error message. Type the command again. When the command is completed successfully, a confirmation appears, followed by a new command prompt. Then, go to step 3.
Type exit, and then press ENTER.

Did this fix the problem?

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

Back to the top

Something to say

Thursday, August 13, 2009

How to reset TCP/IP protocol if it becomes corrupted

How to reset Internet Protocol (TCP/IP)

On This Page

Introduction
One of the components of the Internet connection on your computer is a built-in...

Fix it for me
To fix this problem automatically, click the Fix this problem link. Then click R...