Discussion Locked

4.6 Client for NT problems

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
On a few PCs in my office, the NetWare Client for NT 4.6 (and 4.5) causes the "SPOOLSS.EXE" process to use 40%-70% CPU and sucks memory like there is no tomorrow. Also, the printers folder is unaccessable. It opens, but the window is grey inside andno printers visible. If you try to print, it locks up the OS. It seems like Windows Messaging may be part of the problem because everything works fine if it is not installed, but when it is installed with the GroupWise installation (or before, during the OS installation), the problems begin. If I uninstall the NetWare client and use the Microsoft Client Services for NetWare, there is no problem. Reinstall the NW client, the problem returns. I must use the NetWare client as the MS client can notaccess the Server License Manager for an application we are using. I may be wrong, but the NetWare client also seems to be causing a high utilization problem on my main server. NetWare 4.11. TIA!

9 replies

by damdy

You need to configure your NT server to use NWLINk to talk to the Netware Client and provide services such as printing, file access, ect....
use the network utilities on the control panel of you NT server and add the NWLINK protocol.

by kayode

There is a service Pack 1 on support .novell.com that is supposed to take care of this issue. I had a lot of issues with the NT 4.6 client until i installed the service pack for it. Good luck

Kayode

by don_brill

I'm using the NetWare Client for NT version 4.6 SP2. I didn't experience the problems your describing with 4.60, SP1 or SP2. SP2 appears to handle printing very differently than the previous (for example, you can no longer go to the ports of a connected printer and see what it is...)

I've found it very important to check for older version of DLLs in shared locations on the fileserver and/or workstation. Most notably MFC42.DLL.

Also, as poorly as MicroSoft implements IPX/SPX, I'd recommend removing that protocol from any NT server on the wire - at the very least disable SAPing.

by tvm12

I have NO NT SERVERS!

And I need the mfc42.dll that is installed by AutoCAD or it won't run.

by stanps

I would also recommend at least service pack 5 for NT. If it's already applied... reapply it.

Hope this helps.
Stan :)

This discussion is closed to new replies.