General discussion

Locked

novell 3.2 not-logged-in connections

By Jim Mostowski ·
I have a client who recently started having a problem with not-logged-in (NLI) connections. For no apparent reason, these connections started to appear and keep reappearing after both manually deleting them and when using NLICLEAR.NLM When checking the NIC address on these connections, they come from all known users, not just a few. The client has a 50 user license and currently has 39 regular users and 5 printers (HP jetdirect cards). Any suggestions as to what the problem is and/or how toidentify the cause?

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

novell 3.2 not-logged-in connections

by alan In reply to novell 3.2 not-logged-in ...

I don't mean to answer a question with a question, but were the client machines recently upgraded? Characteristics of using the latest Novell clients in a NW4x or 5x environment will yield authentication connections that seem to multiply with time (from on of the NTS boxes I have). I don't have any experience with NW3.2, but this may be part of the source of problems. Something worth looking at anyway.
HTH
--alan

Collapse -

novell 3.2 not-logged-in connections

by Jim Mostowski In reply to novell 3.2 not-logged-in ...

Poster rated this answer

Collapse -

novell 3.2 not-logged-in connections

by somchai In reply to novell 3.2 not-logged-in ...

This is the normal situation. The users which attach to server but not login would appear as not-loggeed-in. The client software would attach to at least one server (preferred server) even if not login. For NetWare 3, this take a connection (yes, license). For NetWare 4 up, does not take a license.

The example of NLI is, when a computer boot and run driver software, it would be able to see the F:\LOGIN drive, this would shown as NLI on server.

Collapse -

novell 3.2 not-logged-in connections

by Jim Mostowski In reply to novell 3.2 not-logged-in ...

Poster rated this answer

Collapse -

novell 3.2 not-logged-in connections

by wirejockey In reply to novell 3.2 not-logged-in ...

This is normal. If your workstations are Windows 9x or NT, they will attach themselves to the server weather or not the user logs in. If you use DOS workstations and you have times when the user will not need to login to the server, you could createa multiboot situation where the drivers are not loaded. Good Luck!

Collapse -

novell 3.2 not-logged-in connections

by Jim Mostowski In reply to novell 3.2 not-logged-in ...

Poster rated this answer

Collapse -

novell 3.2 not-logged-in connections

by Jim Mostowski In reply to novell 3.2 not-logged-in ...

This question was closed by the author

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums