Discussion Locked

Error 10043 using ping on 95 machine

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

I have a Win95 machine that gives me an error 10043 when trying to ping an ip address or dns name. This seems to be a winsock error, from what I can gather from the MS knowledge base. What causes it and how do I fix it? It is Win95c, with windosck 2. Any suggestions would be greatly appreciated.
Thanks all.

6 replies

by mphoffar

Sounds like you're trying to use the old ping version with the new winsock or visa versa. There should be a directory under windows called ws2bakup with a batch file in there called ws2bakup.bat. Running that will basically uninstall the update. If I get a file sharing message, I usually run the batch at a command prompt.

I'll then remove my TCP/IP stack, sometime add in netbeui so I don't have to get the NIC going again, and reboot. Before reinstalling, I rename the wshtcp.vxd file.This will force a copy of the files from the cab files when you reinstall the stack.

Mark

by mmccaskill69

The error comes up when the TCP/IP stack is unable to initialize. This happens when there are TCP/IP files with a .386 extension in the windows directory.

The fix is to delete or rename the following files found in the windows directory:

vdhcp.386, vip.386, vnbt.386, vtcp.386, vtdi.386.

Do not delete the files if your running AOL.

MM

by tuck46

answer 2 is correct, however after renaming your 386 files uninstall and reinstall tcp/ip.

by wsmith

Thanks folks. I've decided to reformat and reinstall. Hopefully that will clear up all the problems.

This discussion is closed to new replies.