General discussion

Locked

winsock failed to intialize

By jeffw ·
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 **** away the hard drive and start all over. If there is a better way, I need help.
Thank you
Jeff

This conversation is currently closed to new comments.

12 total posts (Page 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

winsock failed to intialize

by jeffw In reply to winsock failed to intiali ...

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 I 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

Collapse -

winsock failed to intialize

by jeffw In reply to winsock failed to intiali ...

This question was closed by the author

Back to Windows Forum
12 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums