Each client connection requires two connections to the server. In the Novell Client for Windows 95 v2.5 and the Novell Client for Windows NT v4.3 and earlier, the "monitored" connection would authenticate to the server and through that connection you would login and create the licensed connection that shows up on the connection list of the server. The monitored connection would then turn into a Not-Logged-In (NLI) connection that you could also see in the server connection list. This method left us with two problems.
1. Admins didn't know what the NLI connections were and would delete them.
2. When the user wanted to log out, the NLI connection would have to be authenticated again so the logout procedure could happen. This could take a long time if the network was having problems.
So the decision was made to leave the monitored connection as an authenticated connection all the time for the NetWare 5 clients. That's OK unless you want to set the concurrent connection limit to 2. If the concurrent connection limit is set to 1, the user logs in on the first machine. The monitored connection is made and before the licensed connection is made, we check the concurrent connection limit. There are actually two checks. The first is when DS checks the number of network address attributes the user object has. In this case, only one - the monitored connection. The next check is to look at the connection table of the server and see how many authenticated connections there are. In this case, only one - the monitored connection. So the user logs in and creates the licensed connection. Now you see two authenticated connections in the server connection list--the monitored connection, still authenticated and identified by the user name, and the licensed connection, also authenticated and identified by the user name. So that works OK.
But when the concurrent connection limit is set to 2, we have a problem. The first time the user logs in everything works as described above. When the user tries to login on the second workstation, this is what happens: The user creates a second monitored connection (from the second workstation where he is logging in). The concurrent connection checks begin and network address attributes are checked. There are only two (only the monitored connection provides a network address attribute to the user object). The next check is performed and the server connection table is checked for authenticated connections. There are now three--the two authenticated connections from the first workstation login and the monitored connection from the second workstation. The login then fails.