Am I correct in believe that the easiest way to get around this error, where users have crashed while connected and they're still authenticated is to disable the account for a short time ?
When I get this error I go to the main connection screen and clear their connection and all is well. The authenticated connection is usually the one that hangs. That is the one with the * before the name.
Hope this helps, Chuck
tek-tips@aspenpkg.com
If you feel a post has been helpful to you, click on the link at the bottom of their post to let them and others know the information was of use.
Which main connections screen ? Is this on the server, if so this is for a 1st line helpdesk (don't laugh.....please!). We only have access to N/W Admin, and no RCONSOLE or such to play with.
Dont worry I wont laugh. We (tek-tip users) have been in the same situation before.
This would be at the server. IF you need me to help walk you through it you can call me at 1-800-367-5493 and ask for Chuck. Chuck
tek-tips@aspenpkg.com
If you feel a post has been helpful to you, click on the link at the bottom of their post to let them and others know the information was of use.
I usually increase the concurrent connections, get the user to logon, then decrease the concurrent connections back to the start figure. I've had no issues with this?
I agree with TheLad, if the Help Desk has the rights to add another connection. What I have done also is give 1 extra concurrent connection than the user needs (in the user template) so as to cut down on that type of call for our Help Desk. We don't have Help Desk staff goto the server (remote or otherwise), that would be passed on to other personnel.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.