ERROR The terminal server has exceeded the maximum number of allowed connections
When a user establishes a Remote Desktop connection to the WHS this connection will remain active until the user selects “Log Off” from the Start Menu. If a user simply closes the remote desktop window when they’re finished, that username will still remain logged on.
The software running on the WHS to facilitate the Remote Desktop connection will only allow for up to two simultaneous sessions. Active and disconnected sessions are calculated in this connection limit as is the Administrator account also. The console session, however, does not count against the connection limit.
If a third attempt is made to login to the server, the dreaded “The terminal server has exceeded the maximum number of allowed connections” error will be shown to the user, and they will be unable to complete the login process. You can’t even connect to disconnect the old sessions BUT there is a way around this:
Simply click OK to the error message and wait for unto 30 seconds for the window to close then simply type the following in a Start – RUN or CMD Prompt on your client machine.
mstsc /v:00.00.00.00 /f -console
Replace 00.00.00.00 with your server’s IP Address or server name. e.g.SERVER
Type in your administrator password. This will then connect you to the Console Session on the server and allow you to remote control the machine again.
Once in Click Start, point to All Programs, point to Administrative Tools, and then click Terminal Services Manager.
In the left hand column you should see your server name. Click on it once. Note the Users Tab in the right pane.
You should see a list of users. You need to reset the two “Disconnected” users. You can do this by right clicking the disconnected user and selecting “Reset.” You should now be able to connect with RDP again after Start – Log Off.
When logging in under this special Console session always kill the inactive sessions first, because if you get disconnected again you will have to connect your monitor, keyboard and mouse.
Only use this session to terminate the other two sessions and not for any other use.
In future when you are done with a Remote Desktop session on WHS, you should always use “Log Off” rather than disconnecting by closing the RD window with the X as this will disconnect from the session but leave it active.
P.S. You could also use the easy option and just reboot the Windows Home Server.
Share this WHS Article with Others:
Entered:
mstsc /v:[remote.ip.address] /f -console
Got:
Sign-in for Remote Desktop
Entered:
Credentials
Got:
“The terminal server has exceeded the number of allowed connections.” Again.
These instructions:
Fail.
The instructions are for Windows Home Server.
Nice fail though Singlestone. If you use the -admin switch instead of -console it should work for Server 2003, etc.
Thanks Bobby, it worked for me
thanks, worked for me the -admin switch
Thanks it works
Thanks for good advice. Worked for me with -admin!
-admin switch is working. Thanks Bobby!!!
Thanks, it works for me. ^^
Thanks a stack Bobby!!!!! You have really been a great help.
Thank-you very much, this worked perfectly.
Worked fine for me on Windows Server 2003 R2. Thanks for a great article!
Thanks for your valuable information. it’s working fine.
[...] of our most read posts here at MSWHS is one which was written back in June of 2007 entitled, “ERROR The terminal server has exceeded the maximum number of allowed connections”. When a user establishes a Remote Desktop connection to the WHS this connection will remain [...]
Works like a charm in 2k3 with
mstsc /v:[remote.ip.address] /f -admin
Thanks for sharing
-console didnt work for me. was almost frustrated till i tried -admin and it, like you said worked like a charm. thanks very much for sharing.
Nice Tip , works for me …
Thanks
Thanks you very much !
I found another solution to work around this problem. you just need to to query the sessions and then reset any session you want and you can easily login: check the under given URL:
http://www.itoperationz.com/2010/10/terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/
Thanks .. a Ton..
Useful Piece of Information
Thanks , I worked . other wise I would have landed in trouble .
[...] WHS – ERROR – The terminal server has exceeded the maximum number of allowed connections… Filed under Tech Bites ← Dude’s – Using Java Threads .Net Bites → [...]
Works Great!
mstsc /v:myserver.no-ip.org /f -admin
Windows Server 2003 Standard
Thanks!
Cool..
Worked like charm…
Thank you.
Struggling with it for awhile, and then read the comments from other user, and it worked. I am on a Vista machine.
Thanks for the helpful tips!
I have Terminal Services Manager installed under Administrative Tools. I highlighted “This Computer” at the top of the list, clicked “Actions” and “Connect to Computer…” and typed in the balky server’s name. The list showing two disconected sessions appeared, allowing me to diconnect them without fully logging into the remote server.
coool…. thanx for such a great tip
THANXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX WORKED FOR ME
Success!
thanks very much it works for me
it worked great. mstsc /v:ip address /f -admin.
Thanks for valuable help.
Thanks a lot for the information, it saved me a lot of time: the server is 50 miles away: no one around to help me,
we have the same problem… they call it save by the miles….
Thanks a lot worked in “mstsc /v:ip address /f -admin”
Thanks a lot worked in “mstsc /v:servername /f -admin”
tnks
Thank you Sir. This info was quite helpful….thanks a lot
[...] cả, nhưng biết là có giải pháp, hôm nay gặp tình trạng trên nên cố gắng tìm giải pháp đó trước khi phải lọ mọ xuống [...]
hi..
it worked for me perfectly
Thnks…
Simply click OK to the error message and wait for unto 30 seconds for the window to close then simply type the following in a Start – RUN or CMD Prompt on your client machine.
mstsc /v:00.00.00.00 /f -console
Replace 00.00.00.00 with your server’s IP Address or server name. e.g.SERVER
Type in your administrator password. This will then connect you to the Console Session on the server and allow you to remote control the machine again.
Thanks, worked a treat!
Thanks pro
-console did not work for me.
-admin WORKED like a charm, and i think more than on Server 2003 – SOLVED.