Very slow at logging on to Server

[cthreepo]

Hi please can you help.

I am running Novel 5.1 with latest versions of client for each respective OS i.e. Win 95, Win 98, Win 2000/XP.

Can anyone tell me why it is taking longer than normal to log on? Nothing intensive is being done across the network.

Thanks,

Jim let's help one another, not hinder.

 

[TheLad]

How have you got the clients configured protocol wise (just IPX, just IP, both etc...).

Do you have any container search policies configured and are they configured to search the whole tree or just a branch? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[cthreepo]

I am using IP Only and there are no container search policies configured.

Any ideas?

Jim let's help one another, not hinder.

 

[TheLad]

Firstly, try putting a preferred server into the Server field in the Advanced properties of the client and see if that helps. Make this server the closest on the LAN if you can.

Sounds like the good old tree walking problem. Check out the TID below. It is quite a big TID but is worth a read:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10051665.htm

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[cthreepo]

Thank you for your help.

Appreciated

let's help one another, not hinder.

 

[ITsmyfault]

FWIW
1- server s/b in same container with users for best speed. The first thing that happens when you try to log in, or print, open a file, etc. is that your client goes looking for a replica that has that object(resource) in it to see where the thing is, and then if you have rights to do what you're trying to do. If there is nothing in your container, you go up and up and up until you get to the root and then you come back down the tree. In extreme cases this can cause 15min logins.. Seriously!! The most common tree design error IMHO is to treat NDS like a DOS file system. I did this myself as well, but have learned the hard way not to do this. NDS is about putting users together with the stuff they use. The less searching, the better. this is the key IMHO and IME.
2- configure SLP if you're using TCP/IP
3- if you have printer captures etc that use a command line, launch them with an "@" not a "#". This allows the login script to complete regardless of how the capture works. (otherwise the login has to wait for the capture to complete)
4- plan carefully where to have replicas and alias objects to help speed access to resources.
hth
Joe

 

[TheLad]

The server does not necessarily have to be in the same container as the users, just as long as your LAN contains a replica of both the container where the users are and the container where the server resides, the system should function like a dream.

SLP is a must for a TCP/IP only network. SLP is the IP equivalent of SAP for IPX (in a fashion). There is loads of useful information on the Novell website, the TID below is an example:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014467.htm

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------