Windows Socket Interface error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am unable to ping anywhere, even my own NIC (127.0.0.1).

One solution for this seems to be the Winsock2 entry in the registry is
missing or corrupt. The solution (Kb 246727) is to delete the key, remove
Dial-up networking and then add Dial-up networking again. However, I do not
have Dial-up networking installed.

Does anyone know of another solution please?

Thanks
 
Dave said:
I am unable to ping anywhere, even my own NIC (127.0.0.1).

One solution for this seems to be the Winsock2 entry in the registry is
missing or corrupt. The solution (Kb 246727) is to delete the key, remove
Dial-up networking and then add Dial-up networking again. However, I do not
have Dial-up networking installed.
Click to expand...

As noted in that article, it only applies to computers that have
Internet Explorer 4 or 5. It doesn't apply to Windows XP, which has
Internet Explorer 6 or 7 and doesn't have an installable component
called Dial-Up Networking.
Does anyone know of another solution please?

Thanks
Click to expand...

Open a command prompt window (Start > Run > cmd), enter this command,
and reboot:

netsh winsock reset catalog

If that doesn't solve the problem, download WinSock XP Fix on another
computer, copy it to your computer, and run it:

http://www.snapfiles.com/get/winsockxpfix.html
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
I am unable to ping anywhere, even my own NIC (127.0.0.1).

One solution for this seems to be the Winsock2 entry in the registry is
missing or corrupt. The solution (Kb 246727) is to delete the key, remove
Dial-up networking and then add Dial-up networking again. However, I do not
have Dial-up networking installed.

Does anyone know of another solution please?

Thanks
Click to expand...

Dave,

There are several procedures for repairing a broken LSP / Winsock. KB246727
isn't the only solution. For Windows XP you can use "netsh winsock reset
catalog", but that's not the only, nor the most effective all of the time.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
 
Back
Top