Sasser after-effects

[S T 824]

I fell victim to the Sasser worm the day it came out.
Before it was established as a "worm", I searced MS's
Knolwedge Base for a solution. I found my exact error
listed, and completed the steps to correct the error I was
getting. Those steps includeded removing WINSOCK and
WINSOCK2 from my registry, under ContrelSet001,
Contro;Set002 and CurrControlSet. I did all that and
rebooted, which refreshed the deleted files.

I have not been able to access the internet, either
through dial-up or DSL since then. It's been a month, and
I'm at my wit's end. When I try to ping an IP address, I
get the error: Operation Was Attempted on Something That
Is Not a Socket" Error Message When You Try to Obtain an
IP Address
I found an atricle with a solution (#318584), but the
solutions do not remove me error - it still occurs. Does
anyone have ANY idea of what to try?

 

[Steve Winograd [MVP]]

I fell victim to the Sasser worm the day it came out.
Before it was established as a "worm", I searced MS's
Knolwedge Base for a solution. I found my exact error
listed, and completed the steps to correct the error I was
getting. Those steps includeded removing WINSOCK and
WINSOCK2 from my registry, under ContrelSet001,
Contro;Set002 and CurrControlSet. I did all that and
rebooted, which refreshed the deleted files.

I have not been able to access the internet, either
through dial-up or DSL since then. It's been a month, and
I'm at my wit's end. When I try to ping an IP address, I
get the error: Operation Was Attempted on Something That
Is Not a Socket" Error Message When You Try to Obtain an
IP Address
I found an atricle with a solution (#318584), but the
solutions do not remove me error - it still occurs. Does
anyone have ANY idea of what to try?

That article only applies to Windows 2000 and 2003. These articles
have XP instructions:

Error message when you try to connect to network: An operation was
attempted on something that is not a socket
http://support.microsoft.com/?id=817571

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/?id=811259
--
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

 

[Mario]

I had a similar problem with Windows 98, after removing winsock, and
rebooting (to refresh the winsock files), I uninstalled TCP/IP, rebooted
again and reinstalled TCP/IP. That fixed it. Good luck..