Networks

Ask something
Discussion Locked

Windows 2000 Professional & Netware NAL

0 helpful
5 replies

by mablair88 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Windows 2000 Professional & Netware NAL
We are currently upgrading our workstations from 95/98 to Windows 2000 Professional. At two locations, the NAL takes at least 3 minutes to load on the Win 2000 workstation and applications on forced run takea very long time to install. (95/98 workstations load very quickly) (These locations are still using Netware 4.11). At a third location the NAL loads very quickly as well as the application installs. (This site is running Netware 5.1). All sites areusing an Application Container located one container up in the tree with replicas of this container on all servers. ZENWORKS 2 policies have been checked and all are identical in regards to search policies. Thoughts anyone? I have checked Novell's Knowledgebase but no solutions that work as yet.

5 replies

by tohara

HERE'S A SUGGESTION. From the Novell site:

10050790 - "NAL is slow with both IP IPX enabled"
Possible Cause: If both IP and IPX are enabled on Windows NT/2000, the workstation will attempt to discover services using both IP and IPX, to determinewhich server is closest. The client will request cost information for both IP and IPX routes. The problem is that if IPX is turned off at the routers, the client will never receive a response to its IPX RIP requests.
Solution: If IPX is not routedacross the network, edit the registry to disable IPX costing on the client so the client will not RIP to discover the cost (hops and ticks) of IPX routes.

by mablair88

IPX is routed across the network so editing the registry to disable IPX COSTING was not a viable solution. The preferred protocol is IPX and IP had been disabled on all Win 95/98 workstations to improve performance. Installing just IPX with the 4.8 client did not solve the problem. Any other suggestions??? I suspect the problem lies in the ZENWORKS policies but I can not place exactly where.

by colin_joseph

Another thing that will make NAL hang is how many containers you have it configured to search for policies. If you have it configured to search more than one container, or groups for NAL policies, then it will take longer to proceed. ALSO, if you have applications that reside on other servers on replicas that are NOT on the server where the workstation connects to, the external references and tree walking will definitely kill you. Try limiting the tree walking and make sure that all applications that you intend to run reside on a replica that is local to where your users will be connecting to.

by mablair88

The problem has been resolved with the install of service patch 3 for the 4.8 Novell Client.

This discussion is closed to new replies.