What exactly is a 'NOT-LOGGED-IN' connection on a 5.0 box

[dsturgeon]

We have a lot of these and I am not a Novell guy so if someone could clue me in I would appreciate it. We have users that cannot log in to the server when there are a lot of these, so I delete them and then users can log in just fine. I am guessing that these connections are using up licenses, and we have involved Novell on this but the issue still exists. I think I would have to open up another ticket (the last one was $300) to resolve this so I am trying the less-expensive option first. Service Pack 6 has been applied. Is there a utility or NLM that should be clearing these out and is not doing its job? If you need more information please let me know.

Thanks. Fish

"Your worst day is only 24 hours long"

 

[TheLad]

A NOT-LOGGED-IN connection is used by a workstation that has been booted up, but is not currently logged in at the moment.

Basically, in order for a PC to log into the network, it needs some sort of connection to the NDS in order for the workstation to be able to check the NDS for the authentication details (username and password). This is what a NOT-LOGGED-IN connection is.

Quote from Novell website:

"A not-logged-in is an attachment. An attachment is NOT a licensed connection. The not-logged-in connection (or attachment) occurs after the shell makes it's connection, but before the you login and enter a password. When you logout the connection returns to a not-logged-in connection. The connection goes completely away if the shell is unloaded or if the watchdog process drops the connection. " -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------