Discussion Locked

slow login after 5.1 upgrade

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
After upgrading a 4.11 server on the WAN to 5.1, login is very slow for users not in the local context. Local 5.1 servers seem to be working fine, and local users at the remote site login without problems.

8 replies

by jackie d.t.

This is a little long because I do not know what protocols you have configured on your NetWare 5.1 server. Remember, NetWare 4.11 used IPX.

First, what protocols are configured on your NetWare 5.1 server? Is it IP with Compatibility Mode? IPX? Or do you have both IPX and IP installed?

I am not sure what you mean by local context. Is your NDS context setup to correlate with your physical network? If so, are you crossing subnets? And what protocols are enabled on the routers. If it isonly IP, is multicast enabled?

You should check the check the NetWare client configuration of the workstations that are slow. If your server is now an IP server, make sure that IP is listed first under the Protocol tab for the NetWare Client andif it is IPX then vice versa.

By default, IPX is faster but it is chatty.

If the new server is configured for IP, I suggest you load SLPDA.NLM (Directory Agent) on the server. If you load the SLPDA, clients can communicate via unicast or multicast. Accept the default configuration for the SLPDA.

Last, go to the workstations and add the IP address of the server to in the Directory Agent box under the Service Location tab of the NetWare client.

Let me know how you make out. I have upgraded a number of 4.x servers.

by bdgray

If you are operating over a WAN it would be a good idea to partition your tree. One partition for each lacation. Once that is done make sure that you have R/R replicatas of each partion at each site. Also, you may need to traing your users in how to use their distinguished names when logging in to prevent excessive tree walking over the WAN.

by akap

The server is running both IP and IPX, just like before the upgrade. Authenticating from a context in another subnet seems to be the problem, as opposed to browsing to find the server. Is it mandatory to configure slp with both protocols on the server? Does 5.1 and nds 7 need a copy of the replica from the other subnet when 4.1 didn't?

by mrjlturner

To add the the above answers, you may also want to check the client version. I've found problems myself w/ users logging into remote 5.1 servers and client 3.2 causing some slowdown. Either backpeddling to 3.1 or up to 3.3 were both found the correct MY issue. This may pose useful to you also...

This discussion is closed to new replies.