We help IT Professionals succeed at work.

TCP/IP Error code 10043?

ibmdoc asked
Last Modified: 2013-12-16
Recently I had to reinstall Windows 95 along with Novell 32bit Intranetware Client Drivers, ver. 2.2.  Everything seems to be ok, except for the TCP/IP drivers.  I have installed, deleted and reinstalled Microsoft's TCP/IP drivers and continue to get the following message when trying to do a ping, tracert, etc.

"Ping: transmit failed. error code 10043"

According to Microsoft, Knowledge base, I have files that end with 386, "*.386" in my windows folder.  They should be in my "Windows\system" folder.  I have verified and corrected accordingly.  THIS IS NOT THE PROBLEM.  Microsoft had no further suggestions.

Watch Question

I guess they meant this:-
Resolving TCP/IP-related errors after upgrading from Windows for Workgroups.
The following errors might occur when trying to use TCP/IP utilities and services after upgrading from Windows for workgroups:
·      A general-protection fault with a blue screen appears after running winipcfg.
·      The ping command reports error 10043, “Stack not initialized.”
·      The IP address cannot be configured when using dialing in to a PPP server.
These kinds of errors occur if old Windows for Workgroups TCP/IP-32 files are in the Windows folder after Windows 95 is installed. This could occur if a user mistakenly attempts to install the TCP/IP-32 files under Windows 95 when Microsoft TCP/IP is already installed. All files for Microsoft TCP/IP under Windows 95 are installed in the Windows SYSTEM folder.
To resolve “Stack Not Initialized” errors
·      Any of the following files should be deleted from the main Windows folder if they appear there:

vip.386vdhcp.386      vnbt.386vtcp.386      vtdi.386
Checking Microsoft TCP/IP device drivers.
The following device VxDs are provided for Microsoft TCP/IP and should be present on the computer in the Windows SYSTEM folder. If any of these files are missing, remove Microsoft TCP/IP in the Network option in Control Panel, and then reinstall it.
Filename      Description

icmp.dll      Provides Windows Sockets support for ping.
vdhcp.386      Provides the DHCP and WINS protocols. This file uses the 32-bit Windows Sockets interface.
vip.386      Provides the Internet Protocol (IP), Internet Control Message Protocol (ICMP), and Address Resolution Protocol (ARP).
vnbt.386      Provides support for NetBIOS over TCP/IP. Used by NetBIOS applications (such as Client for Microsoft Networks) to access NetBIOS over TCP/IP services, including name, session, and datagram services. (Notice that support for NetBIOS over TCP/IP does not involve NetBIOS encapsulation in any packets.)
vtcp.386      Provides the TCP and UDP protocols over IP.
vtdi.386      Provides support to TCP for TDI applications.
wsock.vxd, afvxd.vxd      Provide Windows Sockets-based access to TCP or UDP for sockets. The related DLL and helper files are WSHTCP.VXD and WSOCK32.DLL.
rpclt*.dll, rpcns4.dll, rpcrt4.dll      Provide support for DCE-compliant remote procedure call (RPC). These files are required to support RPC applications.

PSS ID Number: Q140903
Article last modified on 06-23-1998

The information in this article applies to:
 - Microsoft Windows 95
 - Microsoft Windows 98
When you use 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 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.
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.
Delete or rename the following files in the Windows folder:
 - Vdhcp.386
 - Vip.386
 - Vnbt.386
 - Vtcp.386
 - Vtdi.386
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 Windows 95 or 98 versions of the files in the
Windows\System folder.
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
Additional query words: 95
Keywords          : kbnetwork msnets win95
Version           : WINDOWS:95,98
Platform          : WINDOWS
Issue type        : kbprb
Copyright Microsoft Corporation 1998.


the95, if you took time to read the question, you have just re-posted exactly what microsoft told ibmdoc.
This is a total waste of time.

Sorry ibmdoc, but it annoys me when people do not take the time to confirm what they post as an answer is correct or original (not previously published as a comment or shown in the question), I leave it to you as to what response you wish to give.


This is the first time that I have used this service.  It seems kind of neat, but I must agree with iboddy in that if you, (this goes for anyone), answer a question, please read all of the question.  I made a point to put in a commant about Microsoft's soultion and IT WAS IN ALL CAPS, so that hopefully it would stand out a little.  I wonder if we can put things in color so that it stands out even more, perhaps larger fonts..............Just read...........


jboddy:   Thanks for the comment.  Although your answer was not correct, it did lead me to find the answer as well as I learned some stuff that I did not know and that I needed to know.  
My solution:  although all of the files were there, the intranetware Client drivers 2.5, created a backup director with the same files in them.  Well, at least the same names, but not file sizes or dates.  Boy I feel stupid here.  I simply coppied the files back to the correct directory and like magic things started working again.  I also must confes that this was after 3 reinstalls of Win95, easy and quick from the network, several attempts of reinstalling client drivers and TCP/IP stuff and finally after reading your post I went looking for files in other areas.  One more thing, this machine has never had Windows for Workgroups on it, it has always been a 95 machine.  Thanks for your help...................Now let me figure out how to give you the 100 points......

This problem has been solved!
(Unlock this solution with a 7-day Free Trial)