Discussion Locked

winsock failed to intialize

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After changing a name of a computer with Novell client32 loaded I had problems that lead to a win98 setup from the local cab files setup. Now ping will not work or any internet browsing. I have reinstalled Windows twice. copied wsock32, winsock.dll from another computer,and uninstalled the dialup adapter, ethernet card, protocols. clients.Reinstalled all of the above in various order. winipcfg and ping say they can not intialize a winsock socket.
Is this a path issue, version issue,???
I had this issue once before when trying to get rid of a virus that messed with the winsock.dll. I had to blow away the hard drive and start all over. If there is a better way, I need help.
Thank you
Jeff

12 replies

by jyimcse

The nic card may have been set with a different type of ethernet type. Go to network propetiers | network adapter properties | and check your settings there. Have you tried uninstalling client32, the adapter driver and the adapter from the computeritself? Reboot, then install the NIC again. Could it be a bad NIC?

by yagar

Not sure of the version of the Client you are using or if you are using IPX at all but this has happened to me in 95.

On the finicky machine, and they were rare, I had to remove TCP/IP and IPX both. You mention a dial up adapter remove it also. You will get an error when leaving Network Neighborhood saying you network is not complete ignore it. Reboot the computer and install TCP/IP only (for the nic card) then reboot and check TCP/IP (with winipcfg). Then reinstalled IPX (for the nic card) and rebooted. If all has gone well up to here you can reinstall the Dial up adapter

If all has not gone well, remove TCP/IP and IPX again and reboot.

Go to the registry to

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans
and see what is there. There may be several entries 0000 0001 0002 etc. Be careful!!! but I have removed these and let them be rebuilt as I reset up everything.

I must state working in the registry can be dangerous

good luck hope this helps

by dbaideme

1. Remove all clients, services and protocols from Network properties. You can leave the NIC driver.
2. Rename wsock32 and winsock to whatever!!
3. Rename your client32 program folder to whatever you like or change its location!!
4. Now install tcp/ip.
5. Ping away!

by gregory pleau

Quick n'dirty way to reinitialize the Winsock?

1) Delete (or rename) the winsock.dll and wsock32.dll files.

2) Reinstall the web browser (Internet Explorer or Netscape anyway). The browser program will rebuild the Winsock environment

The other thing to note is that Windows will occasionally ask if you want to replace an older file (four times actually) when reinstalling TCP/IP. If you're absolutely dead, tell it to replace them. You'll open up security holes in the Telnet client, but these can be patched by going to Windows Update once the winsock is fixed.

Good Luck

by jeffw

I tried all the above ( in all the replys, including upgrading to newest Browser)techniques before posting this, I was able to access the web when back at the shop. Microsoft gave the answer, Going into the registry and deleteing the registry keys for winsock and winsock2. Removing dial-up and then reinstalling dialup. I also renamed winsock and winsock2 just because.
Article ID: Q246727 was the answer.
Works great now. I think it was the registry that was corrupt. But I do remember saying no to the overwrite on the TCP/IP reinstall. ( Also all the other network components) so I will give you the points
Thanks everyone for all the answers
Jeff

This discussion is closed to new replies.