Winsock2 corruption problem/solution

March 19, 2008 at 9:02 pm Leave a comment

I repaired a Windows XP installation for a client using their OEM CD-ROM. Everything went fine until I tried to connect to the Internet, using either their DSL or backup dial-up connection. Nothing. IPCONFIG /ALL showed on all interfaces.

When I tried to use PING from a command prompt, the error message was Unable to initialize Windows Sockets interface, error code 0.

Since the TCP/IP stack is built in to XP, I couldn’t simply uninstall and then reinstall TCP/IP. I finally found the answer in this MS KB article. The article covers Win XP (SP1 and SP2), Win Server 2003 and Vista, all of which rely on TCP/IP as a core component of the OS.

Short version of the article for this case (with XP with SP2 installed) was to run netsh winsock reset from the command line and reboot.

Worked like a charm.


Entry filed under: Software, Tech Adventures, Technology.

Virtual web development Windows and physical memory

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed

My Flickr Photos

%d bloggers like this: