Networks

Ask something
Discussion Locked

Win2K workstation to Netware 3.2 server

0 helpful
3 replies

by volleyguy4 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Windows 2000 workstation connected to a Netware 3.2 server (which is really 3.12 with Y2K patches). It was setup originally running on Client32 v4.81 with the latest patch. It ran fine for about a month. Mapping drives during login started to fail intermittently. When it is experiencing a problem, it logs the user in (I see the user name on the server's Monitor screen) and after a couple of minutes fails during the mapping. When it's working fine, there is no delay and drives are mapped immediately. I upgraded Client32 to v4.83 with the latest patch. No luck. I have checked the cable, switched to another hub port, replaced the workstation NIC, set the NIC to 10Base-T, half duplex (no autodetect), set the frame type to 802.2 (since that's the only frame type the server is running), set Client32 to use Bindery first instead of NDS, reapplied Win2K service pack 2, and ran bindfix twice. I can login that user from a Win9x PC with no problems. The workstation is connected to an APC UPS. The Win2K event viewer shows an event ID# 12291 (SAM failed to start the TCP/IP or SPX/IPX listening thread). I couldn't find anything in Microsoft's knowledgebase that helped. Any insight would be greatly appreciated. We see no pattern to the frequency of the problem.

3 replies

by pierrejamme

While this finding is for a different client and NetWare (You won't find a lot of mention of NetWare 3.2), I found the following at Novell using "Natural Language" search engine:
There were numerous other possibilites also, I usually don't find anything useful at Microsoft either, even for Windows products!

Solution ID : 1.0.7549596.2315050

Here is the solution: New machine can't see the NetWare network after installing Novell Netware Client 4.6
Re-install the client after removing the current installation.
1. Remove Service: Novell Client for Windows NT
2. Remove Protocols: NWLink IPX/SPX Compatible Transport, which will also automatically remove NWLink NetBIOS
3. Click OK to save bindings and click yes when prompted to reboot. Be sure to Reboot the Machine
4. Re-install Client, watching for prompt for Windows NT setup files, enter path to the Windows NT I386 Setup Files directory
5. Reboot machine as directed, after the install completes

Here is the problem orgoal:
New machine can't see the NetWare network after installing Novell Netware Client 4.6

Error: "NetWare security message: the tree or server can not be found"

Empty Tree window appears when pressing the browse tree button in the NetWare Client for NT login GUI

Error: "Service control manager: A service failed during system startup"

Event Viewer Error: Event ID 7001
"The Novell IPX/SPX Transport interface service depends on the NWLinkSPX/SPXII Protocol service which failed to start because of the following error: The dependency service or group failed to start."

Event Viewer Error: Event ID 7001
"The NWLinkSPX/SPXII Protocol service depends on the NWLinkIPX/SPX Compatible transport protocol service which failed to start because of the following error: The system can not find the file specified."

by volleyguy4

Pierre, thank you for the tip. I did try re-installing Client32 and it didn't help. That's why I upgraded it from 4.81 to 4.83. I forgot to mention also that TCP/IP is running on the network for their DSL access. One of my friends mentioned thatit might be a name resolution issue so I hard coded the IP information into the workstation and that seemed to help. It was getting its IP lease from the DHCP server built into the DSL router. I waited a few days and after 3 days, it disconnected again. I now installed the Microsoft client for Netware and it seems to be working much better. We'll wait and see. Guy...

This discussion is closed to new replies.