Test Methods to Detect Symptoms of a Damaged Winsock2

Have you encountered a message like this “An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket” when trying to discharge the IP address using IPCONFIG? This is the common error message that shows symptom of a damaged Winsocks2. And also Internet explorer may deliver an error message “The page cannot be displayed. 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”.
Below are the test methods to detect symptoms of a damaged Winsocks2:
Go to Support / Tools directory on the XP source files.
1. The first method is to run the netdiag /test:winsock.
• No problem is occurring if it the test says … passed in the end.
2. The second method is by running the Msinfo32
• After running the MSinfo32, click on + by Components
• Next is to click on by Network
• Continuing, click on by Protocol
• Winsocks2 is ok if these sections are generated:
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....
The Winsocks2 is corrupted if the sections above appear different and needs to be fixed.