Winsock Corruption

[dgt]

The Winsock Entries in my registry seem to be corrupted
after a reboot or restart. I can connect to my Internet
Provider but cannot browse unless I do the following:

1. Delete the Winsock and Winsock2 entries from
registry.
2. Reboot.
3. Delete the Winsock2 entry that automatically gets
added.
4. Re install the Winsock entries by installing the
tcpip protocol.

I have attempted the following all of which do not solve
the problem after a reboot:
1. Downloaded a free winfix program.
2. Downloaded some registry entries that are supposed to
help.
3. Run Reg Mechanic to cleanup registry.
4. Run Adaware to clean off spyware.
5. Run Norton to clean viruses.
6. Used the the NetDiag tool.
7. Used the sfc.exe tools.
8. Used msconfig & disabled all startup items.
9. Removed programs I thought were possible culprits.
10. Removed registry entries I thought were culprits.
11. Disabled services that I thought were culprits.

 

[Kelly]

Without knowing which fix you have already tried, this one works. Then
reboot.
Try line 349: http://www.kellys-korner-xp.com/xp_tweaks.htm

Note: Instead of deleting Winsock2, rename it under Services.

If needbe, also run: HijackThis
http://www.spychecker.com/program/hijackthis.html

Good luck and keep us posted!

 

[Jason Tsang]

Goto your command prompt, and type

"netsh winsock reset catalog"

This command resets the Winsock catalog to the default configuration. This
can be useful if a malformed LSP is installed that results in loss of
network connectivity.

 

[dgt]

Thanks Kelly. I actually found it. It was my Sygate
firewall service that seemed to be causing the problem.
I'm going to attempt a reinstall to see if it just got
corrupted along the way. Thanks again!

dgt

 

[dgt]

Thanks. I think I found the problem. Seems like it was
my Sygate Firewall Service that somehow corrupted the
Winsock setting. I've uninstalled, and I'll attempt a
reinstall to see if it just got messedup.

Thanks again.

dgt

 

[Kelly]

Most welcome and hope all goes well. )




Thanks Kelly. I actually found it. It was my Sygate
firewall service that seemed to be causing the problem.
I'm going to attempt a reinstall to see if it just got
corrupted along the way. Thanks again!

dgt

 

[Kelly]

Thanks, Jason. Will try this one. )