zalez Absent Member.
Absent Member.
4235 views

Vista Client double login

Forgive me if anyone thinks this is a double post. I do have a similar thread in the ZCM forum but that is more related to Zenworks. So I decided to post part of my issue here.

I have a fresh install of vista with the novell client and update 4 applied. When ever I login, once I get to the desktop, I get a prompt telling me I am already logged in and do I want to login again. If I say no, I get no mapped drives. If I say yes, I get the error stating the system could not log me in. I can then login again and everything maps fine.

If anyone can shed some light on this it would be greatly appreciated.

Thanks,
Ryan
Labels (1)
0 Likes
15 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Vista Client double login

zalez <zalez@no-mx.forums.novell.com> wrote:

> Forgive me if anyone thinks this is a double post. I do have a similar
> thread in the ZCM forum but that is more related to Zenworks. So I
> decided to post part of my issue here.
>
> I have a fresh install of vista with the novell client and update 4
> applied. When ever I login, once I get to the desktop, I get a prompt
> telling me I am already logged in and do I want to login again. If I
> say no, I get no mapped drives. If I say yes, I get the error stating
> the system could not log me in. I can then login again and everything
> maps fine.
>
> If anyone can shed some light on this it would be greatly appreciated.


This is known to happen in cases where the user information that is
saved in the Novell Client login profile doesn't exactly match the
information of whom you're actually logged into eDirectory as.

The second login prompt you're seeing is supposed to just happen
transparently for the purpose of running Novell login scripts. But
when there is some difference between what's specified in the login
profile & whom you actually ended up logged into eDirectory as, this
second login ends up prompting for information instead.

On the dialog that says "you are already logged on", it should also be
indicating something like "you are already logged on as user.context,
do you want to login as otheruser.andor.othercontext?" What is the
difference, if any, between the two names its showing there?

Aliases (because of the difference between the alias name specified &
the real object you get logged on as) and LDAP Contextless Login
(because the context found via LDAP doesn't necessarily match what's
in the login profile) are two ways I've seen that kind of symptom.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

Hi Alan,

I logged in as a different user this time and when I got the second prompt. It said I was already logged in as the user I just logged in as, do I want to log in as a totally different user (user i tried before, with the wrong context)????? Where is the client pulling this other user info from?

Also, I have the context in the client set a few nodes deep. The user account I use to log in is at the root tree. In xp the client would search the current set context and the go up, is this not true for the vista client?

Thanks,
Ryan

Alan Adams;1473220 wrote:
zalez <zalez@no-mx.forums.novell.com> wrote:

> Forgive me if anyone thinks this is a double post. I do have a similar
> thread in the ZCM forum but that is more related to Zenworks. So I
> decided to post part of my issue here.
>
> I have a fresh install of vista with the novell client and update 4
> applied. When ever I login, once I get to the desktop, I get a prompt
> telling me I am already logged in and do I want to login again. If I
> say no, I get no mapped drives. If I say yes, I get the error stating
> the system could not log me in. I can then login again and everything
> maps fine.
>
> If anyone can shed some light on this it would be greatly appreciated.


This is known to happen in cases where the user information that is
saved in the Novell Client login profile doesn't exactly match the
information of whom you're actually logged into eDirectory as.

The second login prompt you're seeing is supposed to just happen
transparently for the purpose of running Novell login scripts. But
when there is some difference between what's specified in the login
profile & whom you actually ended up logged into eDirectory as, this
second login ends up prompting for information instead.

On the dialog that says "you are already logged on", it should also be
indicating something like "you are already logged on as user.context,
do you want to login as otheruser.andor.othercontext?" What is the
difference, if any, between the two names its showing there?

Aliases (because of the difference between the alias name specified &
the real object you get logged on as) and LDAP Contextless Login
(because the context found via LDAP doesn't necessarily match what's
in the login profile) are two ways I've seen that kind of symptom.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

Ok this what I have tracked down. I deleted the default profile, that is where the other user was coming from. I then logged in as a user from with in the context that is set and it works perfectly. Scripts run perfectly and all of the drives map. I try to log in as a user that is up a few levels (root) and that is when I get the second prompt.

ie: log in as User.Root and get a second prompt asking if I want to login as User.context1.context2

Seems to me that the client on the login to run the script, doesn't want to search up the tree.

Any help on this?


zalez;1473562 wrote:
Hi Alan,

I logged in as a different user this time and when I got the second prompt. It said I was already logged in as the user I just logged in as, do I want to log in as a totally different user (user i tried before, with the wrong context)????? Where is the client pulling this other user info from?

Also, I have the context in the client set a few nodes deep. The user account I use to log in is at the root tree. In xp the client would search the current set context and the go up, is this not true for the vista client?

Thanks,
Ryan
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Vista Client double login

zalez <zalez@no-mx.forums.novell.com> wrote:

> I logged in as a different user this time and when I got the second
> prompt. It said I was already logged in as the user I just logged in
> as, do I want to log in as a totally different user (user i tried
> before, with the wrong context)????? Where is the client pulling this
> other user info from?


The information comes from the "Login Profile"; the same thing that
the Novell Client for XP/2003 calls "Location Profile".

On Vista, when you login as a particular user from the Vista welcome
screen, you've effectively created a login profile for that user which
will save all the eDirectory login settings. e.g. If you entered
"MyUser" in the username field, there is now a login profile for
"MyUser" which saves the eDirectory tree, context, etc., that were
specified when you logged on as "MyUser".

What's supposed to happen once the Windows desktop is coming up is
that the Novell Client will recall "what was the user profile that was
just used for logging on", and will bring up that profile and execute
a Novell login again.

In the intended scenario, because the login profile would describe
exactly the same user as you're currently logged on with, no new login
actually occurs and the login simply runs the login scripts (which was
the goal/intention).

In the case you're describing, it sounds like for some reason the
last-used login profile doesn't describe the user you've logged on as.
e.g. The last-used profile still refers to a prior login, instead of
the login that was just performed.

I don't know why that would be happening. If it were happening on a
machine in front of me, I'd probably start by uninstalling and
re-installing the Novell Client, just to ensure that something about
the login profiles and such simply haven't become corrupted.

> Also, I have the context in the client set a few nodes deep. The user
> account I use to log in is at the root tree. In xp the client would
> search the current set context and the go up, is this not true for the
> vista client?


The only "automatically search a context other than the one I entered"
that I'm familiar with for the Novell Client for XP/2003 are

1) Contextless Login, which searches whatever contextless login is
configured to search, and not specifcially "up",

2) if the user isn't found in the context selected, the Novell Client
will also look for the user in the same context as the object for the
NetWare server you're connected to. Which might happen to be "up",
but could be anywhere in eDirectory.

Both behaviors still exist for the Vista client as well, but you would
have had to configure LDAP Contextless Login same as it had to be
configured on XP/2003, if that's what was searching for the user's
context.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

I forgot to mention in the example that the User.Root does not exist in User.context1.context2
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

I just checked our xp machines and we do not use contextless login. So I assume what happens is #2 on your post. My login name is contained in the root of the tree and so is our netware server. So I assume that is why xp logs in fine for me. For some reason the vista client is not acting the same way.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Vista Client double login

zalez <zalez@no-mx.forums.novell.com> wrote:

> Ok this what I have tracked down. I deleted the default profile, that is
> where the other user was coming from. I then logged in as a user from
> with in the context that is set and it works perfectly. Scripts run
> perfectly and all of the drives map. I try to log in as a user that is
> up a few levels (root) and that is when I get the second prompt.
>
> ie: log in as User.Root and get a second prompt asking if I want to
> login as User.context1.context2
>
> Seems to me that the client on the login to run the script, doesn't
> want to search up the tree.


How is it that you're specifying the eDirectory context on these login
attempts?

Note that each user has their own "Default" login profile, which is
different from the Novell Client for Windows XP/2003.

e.g. If you're currently logged out of Windows, and you type "MyUser"
into the "Username" field, when you subsequently press "Show Advanced
Options" you're looking at the settings that will be used whenever
"MyUser" is the currently entered "Username".

When you then change the "Username" to be "MyOtherUser", the settings
shown when you subsequently press "Show Advanced Options" are specific
to "MyOtherUser"; they're not shared or remembered from what you
entered for "MyUser" as was the case on XP/2003.

So in your description, one thing I'm unclear on is how you specified
the context in each case. e.g. Are you typing in literally
"User.Context1.Context2" in the "Username" field, or just "User" and
then specifying "Context1.Context2" in the "Context:" field under
"Show Advanced Options".

Then subsequently when you login as "OtherUser.Root", again is that
literally "OtherUser.Root" in the "Username" field or just "OtherUser"
and then "Root" in the "Context:" field?

(I'm changing your example to "User" and "OtherUser" since you
clarified that "User.Root" represents a user who doesn't exist under
Context1.Context2, which I took to mean that the common name (CN)
isn't the same between the two cases.)

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

Hi Alan,

I am typing in just "User" and specifying the context in the Advanced Options. I went through and deleted all registry keys pertaining to the user name that was "stuck" and now the double login does not happen except if the user does not exist in the context.

So my guess is now that the first login searches the current context, if the user is not found then it searches the context where the server resides (Which this does seem to work because I can get past the actual login)

Now when it comes to the script running, I get prompted again because my username resides in the same context as the server, not the current set context in Advanced Options.

If I log in as a student, which the reside in the context that is set, the scripts run fine.

So it seems like the "script" login does not search back to the server context?!?

Here is our tree layout:

Root
....Server
....MyUsername
....Context1
........Context2
............StudentUsers

Hopefully I have explained this alittle better. Thanks for all the help you have been giving me.

Ryan


Alan Adams;1475385 wrote:
zalez <zalez@no-mx.forums.novell.com> wrote:

> Ok this what I have tracked down. I deleted the default profile, that is
> where the other user was coming from. I then logged in as a user from
> with in the context that is set and it works perfectly. Scripts run
> perfectly and all of the drives map. I try to log in as a user that is
> up a few levels (root) and that is when I get the second prompt.
>
> ie: log in as User.Root and get a second prompt asking if I want to
> login as User.context1.context2
>
> Seems to me that the client on the login to run the script, doesn't
> want to search up the tree.


How is it that you're specifying the eDirectory context on these login
attempts?

Note that each user has their own "Default" login profile, which is
different from the Novell Client for Windows XP/2003.

e.g. If you're currently logged out of Windows, and you type "MyUser"
into the "Username" field, when you subsequently press "Show Advanced
Options" you're looking at the settings that will be used whenever
"MyUser" is the currently entered "Username".

When you then change the "Username" to be "MyOtherUser", the settings
shown when you subsequently press "Show Advanced Options" are specific
to "MyOtherUser"; they're not shared or remembered from what you
entered for "MyUser" as was the case on XP/2003.

So in your description, one thing I'm unclear on is how you specified
the context in each case. e.g. Are you typing in literally
"User.Context1.Context2" in the "Username" field, or just "User" and
then specifying "Context1.Context2" in the "Context:" field under
"Show Advanced Options".

Then subsequently when you login as "OtherUser.Root", again is that
literally "OtherUser.Root" in the "Username" field or just "OtherUser"
and then "Root" in the "Context:" field?

(I'm changing your example to "User" and "OtherUser" since you
clarified that "User.Root" represents a user who doesn't exist under
Context1.Context2, which I took to mean that the common name (CN)
isn't the same between the two cases.)

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Vista Client double login

zalez <zalez@no-mx.forums.novell.com> wrote:

> So my guess is now that the first login searches the current context,
> if the user is not found then it searches the context where the server
> resides (Which this does seem to work because I can get past the actual
> login)
>
> Now when it comes to the script running, I get prompted again because
> my username resides in the same context as the server, not the current
> set context in Advanced Options.


Do you perhaps also have "Save profile after successful login"
de-selected in the "Default" System Login Profile?

If I successfully login and run scripts for "MyUser" in a particular
context, then logoff from Windows and type in "OtherUser" in the
"Username" field instead of "MyUser", what happens for me is that I'm
prompted to fill out the "Show Advanced Options" section.

Because if I've never logged on as "OtherUser" before, there's no
login profile saved for "OtherUser". (Once I provide the tree and
context for "OtherUser", now that information will be recalled when I
type in "OtherUser" again in the future.)

In order for me to create the scenario you're describing on my own
machine, I would have to intentionally provide the wrong context for
"OtherUser" in the "Context:" field. (In order to make the Novell
Client have to resort to searching in the NCP server object's context,
instead of just in the context I've specified.)

But in your case it sounds like you're reaching that point in some
more "natural" manner. i.e. You never mentioned explicitly providing
the wrong context when entering "MyUserName" into the "Username"
field; it's as though you entered "MyUserName" and the "Context:"
field already has a value for some reason.

Overall I do think you are correct about the fact that "the login
script login doesn't search in the NCP server container like the
initial login does". This leads to a disparity between the
information saved in the login profile and the user whom you're
actually logged on as, thereby creating the same condition as the LDAP
Contextless Login and alias-involved cases I mentioned earlier.

Its just that I'm unclear on what otherwise normal sequence of steps
is actually leading to this outcome you're seeing, because if I
correctly answer all the prompts that come up, I don't get into that
same situation.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

Hi Alan,

I have just tried a different vista machine and the client does prompt for the tree, context and server on the initial login. So is this normal behavior? I really don't want any of our students to have to choose a context but if this is all we can do then so be it.

I am going to start over on the machine that is giving me double prompts and hopefully that will get me to where i can just have students choose their contexts.

Thank you for all of your help.

Ryan
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Vista Client double login

zalez <zalez@no-mx.forums.novell.com> wrote:

> I have just tried a different vista machine and the client does prompt
> for the tree, context and server on the initial login. So is this
> normal behavior? I really don't want any of our students to have to
> choose a context but if this is all we can do then so be it.


In the "Novell Client Properties", on the "System Login Profiles" tab,
double-click on the "Default" login profile to begin editing it.

(Note this is different from the other location for editing login
profiles, which is under the red 'N' "User Administration for MYTREE",
"Login Profile Administration...".)

On the "eDirectory" tab supply the tree name and the student context
(and initial server, if being specified), and make sure the "Save
profile after successful login" is selected. Press OK to save.

Now when a student who has never logged on at this machine before
attempts to login, by default they will get the student context due to
the information you've populated in the system login profile named
"Default".

This does not help the case where you're logging on as some
non-student account ("OtherUser"); you will need to change the context
to the correct context for "OtherUser" using the "Show Advanced
Options" at least one time, else you'll get the login script failure
issue you've described.

But once you've specified this "OtherUser" and the correct context
once, the next time you attempt to login as "OtherUser" on this
machine there will now be a login profile for "OtherUser" saved from
the previous login, which will already have the correct context.

(Even though new student logins will continue to default to the
student context specified in the system login profile.)

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
zalez Absent Member.
Absent Member.

Re: Vista Client double login

Thank you Alan. That did the trick for the students. Thanks again.
0 Likes
finrod Absent Member.
Absent Member.

Re: Vista Client double login

zalez;1473029 wrote:
Forgive me if anyone thinks this is a double post. I do have a similar thread in the ZCM forum but that is more related to Zenworks. So I decided to post part of my issue here.

I have a fresh install of vista with the novell client and update 4 applied. When ever I login, once I get to the desktop, I get a prompt telling me I am already logged in and do I want to login again. If I say no, I get no mapped drives. If I say yes, I get the error stating the system could not log me in. I can then login again and everything maps fine.

If anyone can shed some light on this it would be greatly appreciated.

Thanks,
Ryan


If you are setting this up for a student lab then you want to cut off the login profiles. Go to Novell Client Properties, then the Advanced Login Tab, select the Login Profile List and cut it off. (This is to make sure no one messes with the next change)
Go to the System Login Profiles Tab, click on Default, then the Properties Button, uncheck "Save profile after successful login"
0 Likes
peterdulany Absent Member.
Absent Member.

Re: Vista Client double login

Was there ever any resolution on this? We have the same problems in our district.

Thanks,

Pete



zalez;1475447 wrote:
Hi Alan,

I am typing in just "User" and specifying the context in the Advanced Options. I went through and deleted all registry keys pertaining to the user name that was "stuck" and now the double login does not happen except if the user does not exist in the context.

So my guess is now that the first login searches the current context, if the user is not found then it searches the context where the server resides (Which this does seem to work because I can get past the actual login)

Now when it comes to the script running, I get prompted again because my username resides in the same context as the server, not the current set context in Advanced Options.

If I log in as a student, which the reside in the context that is set, the scripts run fine.

So it seems like the "script" login does not search back to the server context?!?

Here is our tree layout:

Root
....Server
....MyUsername
....Context1
........Context2
............StudentUsers

Hopefully I have explained this alittle better. Thanks for all the help you have been giving me.

Ryan
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.