Computing.Net > Forums > Windows 2000 > Terminal Services problem

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Terminal Services problem

Reply to Message Icon

Name: BNigh
Date: June 20, 2003 at 13:18:49 Pacific
OS: Win2K server
CPU/Ram: Xeon 2GB RAM
Comment:

We have a remote server that is running terminal services that is giving us the "maximum number of connections exceeded" message. Is there a timeout for disconnected sessions and if not does anyone know how to get around the problem without physically being at the server.




Sponsored Link
Ads by Google

Response Number 1
Name: ad
Date: June 20, 2003 at 19:47:23 Pacific
Reply:

got license server?? how many licenses you have it set to?? how many people are on?


0

Response Number 2
Name: BNigh
Date: June 21, 2003 at 11:18:02 Pacific
Reply:

no license server so it only has the two standard connections that it comes with out of the box. We have two disconnected sessions so we cannot get into the box.


0

Response Number 3
Name: SJafiu
Date: June 22, 2003 at 18:59:40 Pacific
Reply:

Look at the Microsoft article :

Error Messages Generated When Logging on with Terminal Services Client. Microsoft Knowledge Base Article - 246109

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q246/1/09.ASP&NoWebContent=1

About the 4th paragraph down, is the error you state and the reason.


Remote Administration mode allow a maximum of 2 concurrent sessions, active or disconnected --- (Or Disconnected)

You MUST Logoff the session in order for the connection to properly terminate and NOT remain in a open state.

If Both Remote Administration sessions are OPEN (disconnected or in use) the only way to reset them is from the Terminal Service Manager locally OR

Terminal into a different Terminal Server and launch Terminal Service Manager from that System to terminste the open sessiosn on the Sysetm that is Not Accepting connections.

Or perform a remote Restart - or schedule a remote restart at a specific time. Just some options. There is NO Time out period for Administrative Connections. But that isn't to say someone doesn't have a registry hack to change that or some other tool.


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: Terminal Services problem

Terminal Services problem www.computing.net/answers/windows-2000/terminal-services-problem/54528.html

VPN/Terminal Services Problem www.computing.net/answers/windows-2000/vpnterminal-services-problem/52182.html

Terminal Services Problem www.computing.net/answers/windows-2000/terminal-services-problem/46779.html