Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
2791 views

Context appears only after login

Help, I've been trying to solve this for over a week now.

Whenever a user logs in they cannot connect to our remote server (-890
error). They have no problems connecting to the server in their
office. While troubleshooting this issue I noticed that the users can
see our tree but cannot see any contexts both when we first (intial
boot) try to login and for a few minutes afterward. Once logged on
after 5 to 10 minutes I can see the contexts and login normally from
the users desktop. I can ping the remote server from the workstation
and office server by name and IP.

Our servers are running NW 6.5 sp5, warkstation clients are 4.91 sp2
and XP
We are running IP only, SLP seems to be running well and the
workstations have the SLPDA set up properly.

To confuse things more one person can connect normally from the office,
I have been trying to match configurations and rights but so far no
luck and the remote office has no problems logging in and connect to
the servers.

Labels (2)
0 Likes
34 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

You sure about that 890 error? It isn't something like 8890 ?

Next time have them try this: delete the tree, context and server name
from the GUI login fields, and just put the desired server IP address in
the server name field. If that works and the server name does not, you
do have an SLP issue.

Also check licensing: You should have an NLS_LSP object for each 6.5
server, in its container. A 6.5 server license object should be in the
same container as the server object(s), or above that in the tree, and
not assigned to any server. If non-MLA, a 6.5 user (conn) license needs
to be in the same container as the user objects, or above that in the
tree, and not assigned to any server. Make sure the two license types
are successfully being consumed.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


Andrew C Taubman wrote:
> You sure about that 890 error? It isn't something like 8890 ?
>


First, thank you for the reply.

The error message is
"LOGIN-LGNWNT32.DLL-890: The specified server is unknown."

I have been thinking this is the result of the same problem that is
stopping me from seeing the context.

> Next time have them try this: delete the tree, context and server name
> from the GUI login fields, and just put the desired server IP address in
> the server name field. If that works and the server name does not, you
> do have an SLP issue.


Once the context is found it logs in normally with just the IP,
otherwise its the same problem.

> Also check licensing: You should have an NLS_LSP object for each 6.5
> server, in its container. A 6.5 server license object should be in the
> same container as the server object(s), or above that in the tree, and
> not assigned to any server. If non-MLA, a 6.5 user (conn) license needs
> to be in the same container as the user objects, or above that in the
> tree, and not assigned to any server. Make sure the two license types
> are successfully being consumed.


The NLS_LSP object is missing from the local server it does have LDAP
Server and LDAP Group though. The NLS_LSP is present for the remote
server. The tree has Novell+Netware 6 server and Novell+Netware 6
user, 1 each. How can I check to see if they are being consumed
properly?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

On Tue, 10 Oct 2006 12:56:28 GMT, "Bill H" <bill@unxinc.com> wrote:

>
>Andrew C Taubman wrote:
>> You sure about that 890 error? It isn't something like 8890 ?
>>

>
>First, thank you for the reply.
>
>The error message is
>"LOGIN-LGNWNT32.DLL-890: The specified server is unknown."


Sounds like the Windows feature that starts the login GINA before the network
driver. What happens if you let the machine sit idle for a minute or two before
the user tries to log in?

---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


David Gersic wrote:
> On Tue, 10 Oct 2006 12:56:28 GMT, "Bill H" <bill@unxinc.com> wrote:


> Sounds like the Windows feature that starts the login GINA before the network
> driver. What happens if you let the machine sit idle for a minute or two before
> the user tries to log in?


If I log onto the workstation and wait about 10 minutes then log into
Novell the problem does not occur. If I wait just at the intial login
request by Novell without going to the workstation the problem is the
same.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


Bill H wrote:
> Andrew C Taubman wrote:


> > Also check licensing: You should have an NLS_LSP object for each 6.5
> > server, in its container. A 6.5 server license object should be in the
> > same container as the server object(s), or above that in the tree, and
> > not assigned to any server. If non-MLA, a 6.5 user (conn) license needs
> > to be in the same container as the user objects, or above that in the
> > tree, and not assigned to any server. Make sure the two license types
> > are successfully being consumed.

>


I ran setupnls and added the missing NLS_LSP. The problem is still
present. Does the server need to be restarted?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

On Tue, 10 Oct 2006 17:38:28 GMT, "Bill H" <bill@unxinc.com> wrote:

>If I log onto the workstation and wait about 10 minutes then log into
>Novell the problem does not occur. If I wait just at the intial login
>request by Novell without going to the workstation the problem is the
>same.


Yep, that sounds like Windows abysmal handling of it's network drivers. Search
for the registry key needed to tell it to wait to start the GINA until after it
has started the network drivers and obtained an IP address.


---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

No.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

On 10/10/06 Bill H wrote:
> The tree has Novell+Netware 6 server and Novell+Netware 6
> user, 1 each. How can I check to see if they are being consumed
> properly?


Hopefully that say "netware 6 + 650", meaning they are for NW 6.5 rather
than 6.0. Those are the license envelopes; open them and that's where
the actual license objects themselves should be. They have names
comprised of a serial number. You can look at those objects in NWadmin
or iManager to see how many licenses are being consumed.

Note that they have to be in the same container as the server or user
objects they are licensing, or above that level in the tree - not to the
side or down the tree.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

Try disabling "Bad Name Cache" and "Bad Address Cache" on the client.
If that helps, we may be able to tweak things to get them working.

Spanning Tree on switches can often cause these symptoms.

Bill H wrote:
> Help, I've been trying to solve this for over a week now.
>
> Whenever a user logs in they cannot connect to our remote server (-890
> error). They have no problems connecting to the server in their
> office. While troubleshooting this issue I noticed that the users can
> see our tree but cannot see any contexts both when we first (intial
> boot) try to login and for a few minutes afterward. Once logged on
> after 5 to 10 minutes I can see the contexts and login normally from
> the users desktop. I can ping the remote server from the workstation
> and office server by name and IP.
>
> Our servers are running NW 6.5 sp5, warkstation clients are 4.91 sp2
> and XP
> We are running IP only, SLP seems to be running well and the
> workstations have the SLPDA set up properly.
>
> To confuse things more one person can connect normally from the office,
> I have been trying to match configurations and rights but so far no
> luck and the remote office has no problems logging in and connect to
> the servers.
>



--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


Andrew C Taubman wrote:
> On 10/10/06 Bill H wrote:
> > The tree has Novell+Netware 6 server and Novell+Netware 6
> > user, 1 each. How can I check to see if they are being consumed
> > properly?

>
> Hopefully that say "netware 6 + 650", meaning they are for NW 6.5 rather
> than 6.0. Those are the license envelopes; open them and that's where
> the actual license objects themselves should be. They have names
> comprised of a serial number. You can look at those objects in NWadmin
> or iManager to see how many licenses are being consumed.


They are both netware 6 + 650 and are above the server level in the
tree. 33 out of 40 are in use and all licenses are present in the same
location. I did notice when I looked at the server licenses that the
remote server (srv1) station was showing an IPX location while the
local server (srv2) was showing an IP location, as it should. When I
removed IPX from srv1 I disabled the protocal and deleted its binding
in inetcfg before restarting the server. srv2 has never had IPX
configured on it. User workstation have had the IPX removed from their
NW Client (reinstalled client chose IP remove IPX if present).

Bill

0 Likes
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


craig wilson wrote:
> Try disabling "Bad Name Cache" and "Bad Address Cache" on the client.
> If that helps, we may be able to tweak things to get them working.
>
> Spanning Tree on switches can often cause these symptoms.


Thanks for your input Craig, Good and bad news with disabling bad
address cach time out. I tried them all at the same time as you stated
above and the problem persists with one change, I no longer have to
wait 5 to 10 minutes I can find the context right away after windows
loads even just reloging into Novell without finding the context first
works after windows loads.

By process of elimination with allot of rebooting I found that
disabling bad address cach time out is what effects this change. I was
never able to login in correctly or find any context in our tree from
the intial nwclient login screen, I can only do this after windows
loads.

Bill

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


David Gersic wrote:
> On Tue, 10 Oct 2006 17:38:28 GMT, "Bill H" <bill@unxinc.com> wrote:
>
> >If I log onto the workstation and wait about 10 minutes then log into
> >Novell the problem does not occur. If I wait just at the intial login
> >request by Novell without going to the workstation the problem is the
> >same.

>
> Yep, that sounds like Windows abysmal handling of it's network drivers. Search
> for the registry key needed to tell it to wait to start the GINA until after it
> has started the network drivers and obtained an IP address.


David thanks for your ideas.
I am having zero luck in finding that registry key to alter the timing.
I have found nwgina entries in my registry and searched the web with no
luck.

Bill

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

Bill H wrote:
> craig wilson wrote:
>> Try disabling "Bad Name Cache" and "Bad Address Cache" on the client.
>> If that helps, we may be able to tweak things to get them working.
>>
>> Spanning Tree on switches can often cause these symptoms.

>
> Thanks for your input Craig, Good and bad news with disabling bad
> address cach time out. I tried them all at the same time as you stated
> above and the problem persists with one change, I no longer have to
> wait 5 to 10 minutes I can find the context right away after windows
> loads even just reloging into Novell without finding the context first
> works after windows loads.
>
> By process of elimination with allot of rebooting I found that
> disabling bad address cach time out is what effects this change. I was
> never able to login in correctly or find any context in our tree from
> the intial nwclient login screen, I can only do this after windows
> loads.
>
> Bill
>


This can be a second issue.

Normally "Public" has at least browse [entry] rights to the tree and
inheritable.

This is what lets you browse and find your context before you logon.
If this permission is removed or blocked, you will not be able to see
contexts until after you login to the tree and get permissions to browse.

I have worked at some places that disable these public rights for
security reasons. However hiding contexts from folks before they logon
is not always a big concern.


--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

> craig wilson wrote:
> This can be a second issue.
>
> Normally "Public" has at least browse [entry] rights to the tree and
> inheritable.
>
> This is what lets you browse and find your context before you logon.
> If this permission is removed or blocked, you will not be able to see
> contexts until after you login to the tree and get permissions to browse.


We would still be able to see the tree?

> I have worked at some places that disable these public rights for
> security reasons. However hiding contexts from folks before they logon
> is not always a big concern.


I have looked into it, there is a Novell TID, public has browse rights
in root and we have never tried to block this. The reason I seem to
link them is when I cannot find context the login script cannot run and
find the remote server; when we find context the script runs perfectly
everytime. Novell TIDs suggested scripting errors however, their fixes
had no effect.

Could this possibly be a replica / partition problem?

Bill

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.