This isn't about a particular problem, but about a trend I've been seeing. Is it just me, or have any of you noticed a lot of winsock problems lately. Any program or client or browser that overwrites the current winsock can throw a workstation into havok. I've seen client32 do it, the windows desktop update, and all kinds of 3rd party programs. when you try to restore the winsock using wsbackup.bat, sometimes it fixes the problems, sometimes it creates new ones, like not being able to ping anymore. The only solution when that happens is to uninstall tcp/ip and client32(IF APPLICABLE), reboot, then reinstall. The problems range from actuall errors to a workstation not being able to shut down. I've seen this problem at so many customer sights that I know it can't be something I'm doing wrong. Especially since most of the networks I work on were put in by someone else. Any comments or suggestions?<br>
<br>
<br>
Joe
<br>
<br>
Joe