my FIX for "WSP Layerd Service Provider wasn't installed as the 1st LSP"

[Barak M. Webb]

Hello all, I've seen several people with the above mentioned problem. After
several days of threads back and forth with Microsoft Support on the Private
DA newsgroup I have finally found a fix.
First I would like to say thank-you to Microsoft for their help and
persistence in assisting me in resolving this issue.

Ok, now for the fix.
The final thread was a request for me to send a copy of my regkey
HKLM\System\CurrentControlSet\Services\WinSock2
After that request I decided that I would export the same regkey from one of
my working computers to my offending computer. Low and behold, I rebooted
and it works now.
If you are going to do this, I would first recommend that you make a backup
copy of your current regkey, then delete the regkey entirely, then merge in
the export from the working machine. I exported the regkey from a computer
that had the same exact OS, services, protocols, and clients that my
offending box.
If you are in doubt of how to use Regedit then first make sure that you have
a good working backup of your entire registry.
This was a fix that worked for me and I don't guarantee that it will work
for you, nor do I accept any responsibility for errors due to misuse of
regedit, (it's a dangerous tool if you don't know how to use it properly.)
If you would like a copy of my regkey that I used, you can e-mail me and I
will e-mail it directly to you. I would rather not put in on the newsgroup
so that no one totally screws up their machine. My e-mail address is
bmw...@ptncs.dns2go.com

[John Tsombakos]

I had tried this too. I copied the regkey from a similarly configured
system. However, it wasn't similar enough. I didn't crash, but the
networking was just hosed. My clean solution was to:

Uninstall Winsock Proxy. Reboot.
Uninstall TCP/IP protocol from the network configuration. DON'T reboot.
Backup, then delete that regkey
(HKLM\System\CurrentControlSet\Services\WinSock2)
Reboot.
Reinstall TCP/IP protocol in Network configuration. Reboot.
Test network connectivity. Should work
Re-Install Winsock Proxy. (Guess what... Yup reboot.)

In article <e02B5vQ4AHA.1808@tkmsftngp04>,

--

John Tsombakos
joh...@ziplink.net * jo...@topsoft.org