Help with protocol error

[858diver]

One of the computers on our 4-machine home network can't connect with the internet. We are sharing a DSL connection with AnalogX Proxy (working great).

The machine in question is able to ping the other machines on the network, including the host with no difficulty whatsoever (typically less than 1 ms, never more than 2).

Have spent HOURS reinstalling network adapters, reinstalling Win98 SE, etc., etc., attempting to repair IE 5, with no success. When I ping an IP address (207.46.103.149 - microsoft.com) at a dos prompt, I get socket error 10043, which the micorsoft knowledge base describes as protocol not supported / the requested protocol has not been configured into the system.

Other than wiping the hard drive clean and starting over, does anyone have any ideas on how go get my daughter back on line?

 

[Captain_Rob]

I found this on 3com's site. I hope it helps.

TCP/IP - Error 10043, Fatal Exception Error, Fatal IP Error


SYMPTOMS


Using the PING or WINIPCFG commands, you may receive "Fatal exception" or "Fatal IP
Error" error messages. Also, the PING command may return the following results:


Pinging 125.50.25.5 with 32 bytes of data:


PING: transmit failed, error code 10043.
PING: transmit failed, error code 10043.
PING: transmit failed, error code 10043.
PING: transmit failed, error code 10043.


CAUSE


The error code 10043 indicates that the TCP/IP stack is not initializing.


This error can occur if you have TCP/IP files with a .386 extension in your Windows folder from the
Windows for Workgroups 32-bit TCP/IP stack.


RESOLUTION


TCP/IP files with a .386 extension are normally stored in the Windows\System folder.
If these files are stored in the Windows folder, they are loaded before the Win95 versions of thefiles in the Windows\System folder.


Delete or rename the following files in the Windows folder:
Vdhcp.386
Vip.386
Vnbt.386
Vtcp.386
Vtdi.386


MORE INFORMATION


The following files with a .386 extension are included with Microsoft TCP/IP for Windows 95 and are
stored in the Windows\System folder:


Name Size Date
------------------------------------
Vdhcp.386 27,961 07-11-95 9:50a
Vip.386 62,614 07-11-95 9:50a
Vnbt.386 95,969 07-11-95 9:50a
Vtcp.386 47,377 07-11-95 9:50a
Vtdi.386 5,687 07-11-95 9:50a

 

[spidey07]

agreed, your IP stack is hosed. The only real way to fix it is by following captain robs/microsoft's fix

cheers

 

[858diver]

Sorry guys - no good

First of all, there were multiple copies of the virtual driver files - one of each in a windows/ws2bakup folder, the other in aol folders. Removal had no effect (after rebooting).

I then went ahead and removed all of the dialup adapters (since there was no longer a modem present), then dialup networking, as well as the network adapter (Linksys PCI card). Upon re-boot, windows saw it, reinstalled the drivers (only asked for the Win98 CD - already had the NIC driver file) and again rebooted.

After re-configuring my network (and rebooting one final time), it is able to see the other machines on the network (under neighborhood network), and can access shared folders, BUT CANNOT PING THEM - still get the same 10043 error!

When explorer gives up, it has the following line at the top:

C:\windows\system\shdoclc.dll/dnserror.htm

In the device manager, the NIC has the following drivers installed, all in the windows\system folder, with .vxd extensions: ndis, vmm32, lnepci2, netbeui, vserver, vredir, nwlink, vserver, vredir, nwredir (just noticed that a couple are in there twice).

As far as my network config is concerned:
Both Microsoft and NetWare clients
NIC
IPX/SPX
NetBEUI
TCP/IP
File Sharing

Bindings:
NIC: IPX/SPX, NetBEUI, TCP/IP
IPX/SPX: Both clients, file sharing
NetBEUI: Microsoft Client, File sharing
TCP/IP: none

As a reminder, DSL line is shared with AnalogX Proxy, which is working great on the other three machines in the network.

Any other suggestions or resources to follow up on?

 

[obenton]

Try this: http://home.tampabay.rr.com/philip1/Windows/win_bugs.htm

 

[Russ]

<< Bindings:
NIC: IPX/SPX, NetBEUI, TCP/IP
IPX/SPX: Both clients, file sharing
NetBEUI: Microsoft Client, File sharing
TCP/IP: none >>



Can I assume from the last line in this list that you have TCP/IP appearing all by itself in the list of installed network components? If this is correct, it appears that you have two stacks. That may be the problem.

Russ, NCNE

 

[Captain_Rob]

<< windows/ws2bakup folder >>


Sounds like you have an old Win95 system you upgraded to Win98SE. That ws2bakup folder is normally only there after loading the Win95 Winsock 2 update. Personally I wouldn't waste a lot of time on trying to recover a blown Windows system unless it was to recover data. If you do have data you need to offload to another network share before wiping the drive, you could reinstall Windows to a new folder. There's nothing like a fresh reload, especially compared to a Win95 to Win98 upgrade.

I'm really just shooting in the dark here, but here are a couple of other things I would try before I would give up and do a fresh reload. Try removing your drivers like you did, but also find and remove the .inf file for the NIC out of the \windows\inf folder. If you don't know the proper .inf file, you can usually find it via find files, text search, &quot;NIC description as displayed&quot;. Removing the .inf should force it to ask for the driver disk on redetect. You might also try to run Microsoft's RegClean program.

 

[858diver]

Russ:

I'm not completely sure what you mean by &quot;TCP/IP appearing all by itself&quot;. All of the subject protocols are present, but there is only one TCP/IP, as I deleted the dialup and AOL adapters. I removed all bindings from this item, as I have been told it is important for security.

Capt:

Yup, this machine was upgraded from Win 95. Just may end up wiping the driving and starting over, after trying some of the EXCELLENT suggestions offered here.

Thanks again all!

 

[858diver]

The bad news is that none of this seems to help, so I am getting ready to wipe the drive and start over with a fresh install Unless, of course someone has any other last attempts.

The good news is that the link provided by obenton is AWESOME. By manually adding the virtual drivers NOT INSTALLED BY WIN98, two of my other machines do indeed seem to run much faster! Thanks!

 

[puritan]

I hate to say it but you can back up, reload, and restore apps faster than all the troubleshooting and as someone said above, it WILL be way more stable.

Sorry