mliong
asked on
NT4 slow on Netware 3.12
I have started to deploy Windows NT 4.0 Workstation on a Netware 3.12 network. My problem is that it takes forever for NT 4.0 to print anything over the network. Network access is also slow, at best.
All NT Workstations are Pentium PCs with 32MB RAM, and are running on SP1 and SP2 (mixed combination). The network is a netware 3.12. The protocol is IPX, but the NT workstations are coming on line with TCP/IP since we will be migrating to that protocol to access the dabase on Unix.
I have an NT server to act as a PDC so that I can centralize the TCP/IP address administration, as well as user accounts on the NT domain. Logging into the NT domain itself is lightning fast, but anytime I do anything related to novell, such as accessing the files on the novell server, or printing through their print queues, it's turtle city.
The performance is slow whether or not I use Client for Netware Networks (MS), or Novell's Intranetware client for NT. I do not use the NT Server to route the requests through GSNW either. The version of the Intranetware client currently installed is v4.0 (961104). Upgrading to the later version did not solve the problem either.
The protocols running on the network are TCP/IP and IPX. Binding NETBEUI over the IPX did not make any difference to the speed of network access.
Does anyone know how I can improve the performance of NT on this network from hell? I'm stuck with Netware because of the corporate direction - but I can influence the desktop systems, and I beleive NT is the future of corporate computing.
All NT Workstations are Pentium PCs with 32MB RAM, and are running on SP1 and SP2 (mixed combination). The network is a netware 3.12. The protocol is IPX, but the NT workstations are coming on line with TCP/IP since we will be migrating to that protocol to access the dabase on Unix.
I have an NT server to act as a PDC so that I can centralize the TCP/IP address administration, as well as user accounts on the NT domain. Logging into the NT domain itself is lightning fast, but anytime I do anything related to novell, such as accessing the files on the novell server, or printing through their print queues, it's turtle city.
The performance is slow whether or not I use Client for Netware Networks (MS), or Novell's Intranetware client for NT. I do not use the NT Server to route the requests through GSNW either. The version of the Intranetware client currently installed is v4.0 (961104). Upgrading to the later version did not solve the problem either.
The protocols running on the network are TCP/IP and IPX. Binding NETBEUI over the IPX did not make any difference to the speed of network access.
Does anyone know how I can improve the performance of NT on this network from hell? I'm stuck with Netware because of the corporate direction - but I can influence the desktop systems, and I beleive NT is the future of corporate computing.
I have noticed similar problems with Win95/NT and LANtastic (speaking of a "network from hell"): I my case I think the problem was (and still is) the mixture of 16 and 32 bit platforms... I don't know netware 3.12, so perhaps this is not applicable for you.
I am assuming that you have installed GSNW on the PDC and not CNSW on all of the workstations, and here lies your problem. NT Servers DO NOT route terribly well.
The only way to get good performance from a mixed 3.12 and NT environment is to use Novells Intranetware client and run IPX on the workstations. You should also enable packet burst mode on the netware redirector to further increase performance.
Hope this helps.
The only way to get good performance from a mixed 3.12 and NT environment is to use Novells Intranetware client and run IPX on the workstations. You should also enable packet burst mode on the netware redirector to further increase performance.
Hope this helps.
ASKER
Edited text of question
ASKER
Sorry for not adding the part about the NT workstations running Intranetware client for Windows NT. These workstations are already running under IPX. Selecting Auto or Forcing the workstations to run on a particular frame type does not make a difference either.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.