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