Newdotnet is not the only cause of this Winsock LSP problem.
And, the fix can be far easier than system restore, which is going to put
back the malware.
In XP SP2,
netsh winsock reset
at a command prompt should do the job, after a restart.
In Windows 2000, there is a KB article explaining how to do this I
believe--cited in other messages in this group.
It is a significant issue for the users affected, but the fix isn't too
arcane or hard to find.