Anonymous_User Absent Member.
Absent Member.
932 views

Client login settings, tree vs server

I know there is a client32 forum, but more people seem to hang out here.

What is the difference between putting in a Tree name and/or a Server name
in client32 login screen?

If I just put a Tree name in I notice my logins take several seconds longer
than if I put in a Tree and a Server name. I have SLP properly setup.
Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Client login settings, tree vs server

Some times putting in the servers IP address instead of the server name speeds up login. A lot depends on your Novell environment, PC configuration, Client configuration, etc. More details would help.

What Windows version are you using, What Novell Server Version, etc?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client login settings, tree vs server

Windows XP. Client32 SP2(some patches). Netware 6.5sp5/6. We have 100's of
servers and thousands of workstations, so we don't have total consistency
but that is about right.

Reason we were wondering is we started getting some NMAS 1644 timeout errors
on our clients randomly. We are not running eDirectory 8.8 and have not
replicated Security. We believe our Root servers are just getting a little
overloaded and are working on that.

When troubleshooting I noticed that if I put a server in Client32 the logins
are much faster. Right now we only put our Tree in, and I always thought
SLP would hand back a server to the client, correct?

We distribute one client package to all workstations, so we are not in a
posistion to put server names in the client, as too big a selection as to
which one. We are thinking of setting up a CNAME and round-robin all our
Root servers with Security container and just bypassing the clients logging
into their local servers, since they have to tree-walk back to Root anyway
for the Security container.

Christopher Premo wrote:

> Some times putting in the servers IP address instead of the server name
> speeds up login. A lot depends on your Novell environment, PC
> configuration, Client configuration, etc. More details would help.
>
> What Windows version are you using, What Novell Server Version, etc?


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client login settings, tree vs server

Is everyone on the same Tree? We put in the "master" Server name for the OU that the employee is logging into. We also configure the SLP portion of the client. If you use ZEN, you can push the configuration out for "OU Groups". We haven't installed ZEN yet and manually configure or workstations (about 300). Further, we only have one tree and 4 File servers that the employees log into.



On 5/31/2007 at 3:53 AM, Mark Feines<xxx@xxx.xxx> wrote:

Windows XP. Client32 SP2(some patches). Netware 6.5sp5/6. We have 100's of
servers and thousands of workstations, so we don't have total consistency
but that is about right.

Reason we were wondering is we started getting some NMAS 1644 timeout errors
on our clients randomly. We are not running eDirectory 8.8 and have not
replicated Security. We believe our Root servers are just getting a little
overloaded and are working on that.

When troubleshooting I noticed that if I put a server in Client32 the logins
are much faster. Right now we only put our Tree in, and I always thought
SLP would hand back a server to the client, correct?

We distribute one client package to all workstations, so we are not in a
posistion to put server names in the client, as too big a selection as to
which one. We are thinking of setting up a CNAME and round-robin all our
Root servers with Security container and just bypassing the clients logging
into their local servers, since they have to tree-walk back to Root anyway
for the Security container.

Christopher Premo wrote:


> Some times putting in the servers IP address instead of the server name
> speeds up login. A lot depends on your Novell environment, PC
> configuration, Client configuration, etc. More details would help.
>
> What Windows version are you using, What Novell Server Version, etc?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client login settings, tree vs server

Jumping in here. We have about 70 servers users log into. We just put the
tree name. Though I know it seems to be faster if client32 can go directly
to a server. Not sure why. Maybe bypassing slp returning a server?? We are
considering removing all our local replicas and adding some more root
servers and just pointing everyone there. How our vlan structure has
evolved over the years at the university sometimes a persons local server
on their floor may be further away than core servers. Of course we would
also benefit from the users not having to tree walk for the UP policies.

Anyway

Christopher Premo wrote:

> Is everyone on the same Tree? We put in the "master" Server name for the
> OU that the employee is logging into. We also configure the SLP portion
> of the client. If you use ZEN, you can push the configuration out for "OU
> Groups". We haven't installed ZEN yet and manually configure or
> workstations (about 300). Further, we only have one tree and 4 File
> servers that the employees log into.
>
>
>
> On 5/31/2007 at 3:53 AM, Mark Feines<xxx@xxx.xxx> wrote:
>
> Windows XP. Client32 SP2(some patches). Netware 6.5sp5/6. We have 100's of
> servers and thousands of workstations, so we don't have total consistency
> but that is about right.
>
> Reason we were wondering is we started getting some NMAS 1644 timeout
> errors on our clients randomly. We are not running eDirectory 8.8 and have
> not replicated Security. We believe our Root servers are just getting a
> little overloaded and are working on that.
>
> When troubleshooting I noticed that if I put a server in Client32 the
> logins are much faster. Right now we only put our Tree in, and I always
> thought SLP would hand back a server to the client, correct?
>
> We distribute one client package to all workstations, so we are not in a
> posistion to put server names in the client, as too big a selection as to
> which one. We are thinking of setting up a CNAME and round-robin all our
> Root servers with Security container and just bypassing the clients
> logging into their local servers, since they have to tree-walk back to
> Root anyway for the Security container.
>
> Christopher Premo wrote:
>
>> Some times putting in the servers IP address instead of the server name
>> speeds up login. A lot depends on your Novell environment, PC
>> configuration, Client configuration, etc. More details would help.
>>
>> What Windows version are you using, What Novell Server Version, etc?


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client login settings, tree vs server

If you know beforehand what server a user will need for login, it is
always preferrable to provide that server in the login properties. This
will avoid that the client will first connect to different servers in your
tree until it finally gets to the server it really needs.
My guess is that your slowness in the tree scenario is really due to some
extra connections to potentially slow servers.
Notwe that the preferred server specificed in the login window should
always point to a server with a r/w or master replica. If you point to a
server with no replica, the login will once again have to go and search
for different servers.
Also, when NMAS is involved, be sure you understand the NDS design
considerations for login speed. Esepcially, if you don't use password self
service, you should absolutely disable the "did you forget your password"
option in the latest clients. For more details, see:

http://wiki.novell.com/index.php/Universal_Password

--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.