Discussion Locked

You are trying to log onto too many...

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

As part of a Network Support team which has recently upgraded from Netware 4 to Netware 5 running Windows NT 4.0 workstations, we seem to be getting an increasing number of calls from users saying that they are getting 'You are trying to log into too many workstations' error messages. upon checking NWAdmin for the number of concurrencies that the user has, I have found that the system shows them having more connections than they are logged in as. Its as if when the user logged out previously the IPX address shown has not been released. When I check remote console for the server and user it does not show any connections???

Does anyone have any ideas?

9 replies

by still_learning

I have seen this happen when the user is logged on and reboots their system. The system reboots and the user tries to log on but this happens faster then Novell is able to detect that they are no longer logged on and release the connection. The other scenario is that they are logging onto multiple servers (because they are mapping to drives on other servers). I believe that each server uses a connection. Good luck - Steve

by tracyp

We also have a Novel 5.1 w/ NT 4.0 workstations. when you set the Novell client did you choose, IP, IPX or both IP/IPX? The connections in rconsole show two connections for each user one with an * in front of the user name. We have set concurrentconnections under login restrictions to 3 for each user and that has helped.

by curtis

We have been running Netware 5 for about 2 years and have found that the only way to stop from having these errors is to run dsrepair every morning and part of the daily server maintenance. I do it right after i change the tapes as part of my routine ...

This saves from compromizing security by increasing concurrent logon connections.

Run DSREPAIR at each Novell server.
At the System Console type ?DSREPAIR ?N1?
Arrow down to Advanced Options Menu. Enter
Arrow down to Repair Local DS Database. Enter
Arrow down to Rebuild operational schema? Hit ?Y?, Enter
Hit F10 to Perform Repair
Be sure ?Yes? is highlighted in ?Repair Directory?? window. Enter
After observing several screen changes, arrow down to ?Yes, save the repaired database? in the Save The Repaired Database? (DIB) window. Enter
In the Repair Process Completed window, notice the amount of errors. Enter
Hit ?Escape? until ?Exit DSRepair?? window appears, make sure ?Yes? is highlighted. Enter.

Works for us ...

by peterst

We're a Netware 4 shop, and experienced this problem as soon as we started using win95. Seems that when the workstation is rebooted, the connection is not immediately dumped, so if the user logs back in streight away they get the message. Also happens when the machine crashes.

We got around it by granting all users 2 concurrent connections, however this may not be a suitable solution in your area.

We dont seem to have seen much of this problem lately, so I'd guess it may have been resolved by a later version of the Netware Client.

Are you using the Novell Netware client? If so, try an upgrade to the latest ver.

This discussion is closed to new replies.