Error: "ping; transmit failed, error code 10045"
(Last modified: 09Oct2002)
This document (10013609) is provided subject to the disclaimer at the end of this document.
fact
Formerly TID 2942877
Novell NetWare 5.0
Winsock2 Update with Client32
symptom
Error: "ping; transmit failed, error code 10045"
Error: "ping; transport failed, error code 10043."
Error: "ping; transmit failed, error code 10091"
fact
TCP/IP problems after upgrading Client32 3.x.
Windows95 workstation crashed during the install of a the 3.0 client.
After rebooting and reinstalling the client the TCP/IP stack became unusable.
If a connection is made with IP from the client to the server the connection is slow.
IP connection to the server is slow.
IPX connectivity is ok.
change
Reinstalled Client32
cause
As part of the client installation, WS2Setup.EXE is executed from the install directory of the client. This is a Microsoft program that updates the workstations's WSock32.DLL and related files to be Winsock 2 compliant. It also creates a backup of the previous winsock configuration, and saves it in the \<drive>\<windows directory>\WS2BAKUP directory. Corruption in the IP stack is sometimes caused by this upgrade.
fix
Do the following:
1 - Try running WS2BAKUP.BAT to see if it is a Winsock2 problem.
If it is a Winsock2 problem, apply Winsock version 2.
1 - Remove the Microsoft TCP/IP protocol
2 - Reboot
3 - Re-Add Microsoft TCP/IP protocol and configure appropriately for the environment.
4 - Reboot
If the preceding steps do not work, try the following:
1 - Uninstall the 3.x client using UNC32.EXE
2 - Reboot
3 - Reinstall the NetWare Client.
4 - Repeat the steps above.
Another customer
Microsoft document Q191064 provides another solution to this problem it states:
" At the command prompt, type the following commands, pressing ENTER after each command
cd\<windows>\ws2bakup
ws2bakup.bat
exit"
NOTE: If you receive sharing violation error messages when you run the Ws2bakup.bat file, reboot to DOS and then perform the above steps.
If performing the above steps do not restore the ip stack to a functional state, try installing something on your workstation that installs a Winsock2 compliant ip stack. For example, installing Microsoft Dial Up Networking version 1.3 will install the a winsock 2 compliant ip stack. Download and install MSDUN13.EXE from MicroSoft's website. You can delete the dial up adapter from control panel, network, and keep the ip stack.
Another option is to download the winsock 2 update from microsofts home page and install that after installing the client.
document
| Document Title: | Error: "ping; transmit failed, error code 10045" |
| Document ID: | 10013609 |
| Solution ID: | 4.0.13676238.2261273 |
| Creation Date: | 04Aug1999 |
| Modified Date: | 09Oct2002 |
| Novell Product Class: | Connectivity Products NetWare Novell BorderManager Services Novell eDirectory |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.