Windows XP Notworking - Sockets Errors

[Guest]

Running Windows XP home SP2 with a single internet connection through adsl
modem.
Every so often my internet connection fails and when I try to ping anything
(incl 127.0.0.1) I get "Unable to initialise windows socket interface". The
only way I can get things working again is by re-insatlling XP , followed by
service pack 2 etc etc.

 

[Lance]

This is often a sign that something (like spyware/adware) is modifying
winsock. Have you run Spybot or Ad-Aware to remove that stuff? Since it
keeps re-occurring, it's a sign that it's being re-installed over and
over again.

If Spybot or Ad-Aware can't fix things up, then try the following.
Resetting winsock and the tcp/ip stack may break some networking
software like Cisco VPN or Novell Client. In that case a reinstall of
the broken software will be necessary.

Lance
*****

Microsoft Knowledge Base Article - 811259
How to determine and recover from Winsock2 corruption
<http://support.microsoft.com/default.aspx?scid=kb;en-us;811259&Product=winxp>

Guy thought carefully and wrote on 10/3/2004 5:55 AM:

 

[Chuck]

Running Windows XP home SP2 with a single internet connection through adsl
modem.
Every so often my internet connection fails and when I try to ping anything
(incl 127.0.0.1) I get "Unable to initialise windows socket interface". The
only way I can get things working again is by re-insatlling XP , followed by
service pack 2 etc etc.

Give LSP-Fix and WinsockXPFix <http://www.cexx.org/lspfix.htm>, or WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257> a shot.

For XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog" into the
command window.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Thanks for quick replies,

I think this problem could well be caused , as Lance says, by adware /
spyware removal software.
The next time I get the problem i'll try the winsock reset.

Thanks,

Guy