6 replies
by pererap01
by deltree
by pererap01
by mphoffar
I think 1 is right in saying the fault is in the stack, however I think reinstalling caused it. I've usually seen this when someone loads the winsock2 update and it went awry. Usually it happens when executbales, like ping, are loaded for one version of a winsock and a different winsock is loaded.
You probobly should run the ws2bakup.bat from c:\windows\ws2bakup and then reload the TCP/IP protocol.
If you have to, rename the wshtcp.vxd file and then reload TCP/IP. This should force copying from the cabs.
Good luck to you
Mark
by pererap01
by pererap01
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending