The symptoms of winsock2 damaged and how to repair

Winsock2 is windows socket version 2, treatment means network transport controller. it use tcp/ip or udp protocols. If it was damaged, you could not conncet to the internet.If you find following symptoms, your winsock would be damage.

1. it is too long that DHCP client obtain the IP address.The client don’t obtain correct IP address at last. The system maybe give your some 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.
(2). An error occurred while renewing interface local area connection: The operation failed since no adapter is in the state permissible for this operation.
(3). An error occurred while renewing interface Local Area Connection: the requested service provider could not be loaded or initialized.
(4). An error occurred while renewing interface ‘Internet’: An operation was attempted on something that is not a socket.
(5). The attempted operation is not supported for the type of object referenced.

2. When you start the Internet Explorer, you will get following messages: ” The page cannot be displayed”
3. Others messages:
(1). Initialization function INITHELPERDLL in XXXXX.DLL failed to start with error code 10107
(2). you may have no ip address or no APIPA(Automatic Private IP addressing) ; you maybe recieving ip packets but not sending them.
4. Using dial-up connection, “Error 720: No PPP Control Protocols configured”—error message is be recieved.
5. In Device Manager,when you click Show Hidden Device,the TCP/IP Protocol Driver is listed as disabled under Non-Plug and Play drivers, and you recieve error code 24.

These issues may occur if the Winsock registry keys are damaged or corrupted.
Use some tools to check winsock2.
1. Use the NetDiag tool.
(1) the netdiag tool is one of MicroSoft Windows XP Support Tools. To use it ,you must have installed the Support tools.
(2) the support tools is on the Windows XP installed CD.
(3) when the installation is complete, you can run this tool.
(4) In command prompt , you enter “netdiag /test:winsock” and press enter. the tools return the test results.
(5) For more detail results, you may use the parameter “/v”. The command is “netdiag /test:winsock /v”.

2. Use the Msinfo32 tool.
The Msinfo32 is included in the standard windows xp installation. It is not necessary that you extra install the Microsoft Windows XP Support Tools .
(1) Run Msinfo32
(2) expand the “Compoments” ,expand the “Networks” and click “Protocols”.
(3) you can find about 10 sections that the section headings include the “MSAFD” or “RSVP”
the following list is normal winsock2 key
MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [DeviceNetBT_Tcpip…
MSAFD NetBIOS [DeviceNetBT_Tcpip…
MSAFD NetBIOS [DeviceNetBT_Tcpip…
MSAFD NetBIOS [DeviceNetBT_Tcpip…
MSAFD NetBIOS [DeviceNetBT_Tcpip…
MSAFD NetBIOS [DeviceNetBT_Tcpip…

if the names are different from above lists , the winsock2 key is corrupted, or you have a third-part add-on.For example ,if you have installed the vmware, you will find the section headings including “VMCI”.
If there are fewer than ten sections, there is information missing.
if you install the other protocols,there are more than ten sections.

To repair your winsock2 ,follow these steps
1. Use Microsoft Fix it Tools
(1) Download this tools from microsoft website,and save this tool to a flash drive or a CD.
(2) Run this tool on the winsock2 damaged computer.

2. Use Netsh command
(1). If your operation system is Windows XP , you must install the Service Pack 2.
(2). In the Command Prompt , type “netsh winsock reset” and press enter.
(3). Reboot your computer.
(4). If you use the Vista or win7 ,run the command prompt as Administrator.

3. Reinstall the Tcp/Ip Protocols
(1). Run the registry editor tool–“regedit”.
(2). In the editor,find the following key ,and delete these key.

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock2

(3). Reboot the computer. This step must be done.
(4). Find the “nettcpip.inf” . there is this file in the “c:windowsinf”.
(5). Open this file with notepad.exe. (In Vista or Win7, you may run the notepad.exe as Administrator)
(6). Find this section “[MS_TCPIP.PrimaryInstall]”. there is the key “Characteristics” in the section.
(7). Change “0xa0” to “0x80” . This step makes sure to get the privilege of modifying the TCP/IP Protocol.
(8). Right-click the network connection, click the properties,then click “Internet Protocol Version 4 (TCP/IPv4)”.
(9). You find that the “Uninstall” button is not gray out. click Uninstall button to complete uninstall the protocol.
(10). Reboot the computer.
(11). Open the properties of network connection again.
(12). click the install button,choose the protocol,click “From the disk”, choose the “nettcpip.inf” and click “OK” to install it.
(13). Reboot the computer again.

I believe that your winsock is normal after you complete those steps. If it is still abnormal, you may reinstall the whole windows system. Good luck.