Terminal server has exceeded maximum number of allowed connection – how to kill open sessions?

Published on May 29, 2009 in windows. 23 Comments Tags: windows.

When you RDC (connecting remotely using Remote Desktop Connection) to a server and get “Terminal server has exceeded maximum number of allowed connection” message there’s still light at the end of the tunnel.

Solution (tested on Windows 2003)

RDC to another server in the same workgroup as the one you cannot access and go to Administrative Tools / Terminal Services Manager.

From the menu select Actions / Connet to Computer… and provide the name of the server you couldn’t reach. Press OK and you will see open sessions on that server – users who logged in but for some reason haven’t logged out. Right click on the desired user and choose Log Off.

That should solve the case.

Enjoy this Post?

Your vote will help me grow this site and provide even more information

23 Responses to “Terminal server has exceeded maximum number of allowed connection – how to kill open sessions?”

Feed for this Entry Trackback Address

ra
July 2, 2009 at 23:36

Thanks, very helpfull
Spectr3
July 14, 2009 at 8:50

Thanks, sorted it out in a minute!
David
August 21, 2009 at 15:55

Very helpful. Thanks.
murukessan
September 2, 2009 at 13:22

great information
we were trying to bring up a remote system whose connection was lost
and it was very helpful
Saurabh
September 11, 2009 at 17:25

I worked in a flash. Great resolution.

Thx.
Amit Goyal
September 29, 2009 at 8:25

Thanks, Great Information.
VenkatMOSS
October 31, 2009 at 14:43

It helped me to keep my schedule on track.

Thanks alot for solution.
RAJU
November 3, 2009 at 14:27

Hi,

1) Can we anticipating any LDAP server authenticating the clients at the Terminal server?

2) Is there any way to run a standby Terminal server?

3) Typically how many clients can be involved in a connection? if so how to do it ?

4) Do the SSH clients predetermined to run only from a specific machines? as opposed to any machine? if so how to proceed it?
Lokesh Sahu
December 1, 2009 at 7:31

Many Thanks!!!!!!!!
rishi
December 7, 2009 at 19:35

hi guys,

This solution doesn’t work if you’re an administrator, any other advice or suggestions?
Randy
January 22, 2010 at 19:02

Thanks a lot…
Ed Rabaya
February 12, 2010 at 5:27

this is of great help, thanks a lot!
Dandabass
February 25, 2010 at 17:26

yep, works!
Kashi Nath Shukla
March 7, 2010 at 4:39

i have already done this but yet tis error is coming
Pankaj
March 19, 2010 at 10:50

Really working and time saving.
Thank you, PROFFESIONALLY!
Anthony
March 22, 2010 at 22:06

Thank you! I was getting so tired of having to ask my manager to log off the server so that I could get onto it when I got disconnected without logging out. Now I don’t have to do that any more.

Thank You!
JiM
April 27, 2010 at 8:32

Thanx for the clear and precise instructions. It worked great.
Aparna Naveen
May 11, 2010 at 20:59

Thanks it was so very helpful.. it worked GREAT!
JJH
May 20, 2010 at 18:35

Thanks for this! I tried “mstsc /v:00.00.00.00 /f -console” recommended on other sites and it didn’t work, but your trick solved it!
Jay
June 2, 2010 at 8:06

thanks mate, very helpful
ajit
July 28, 2010 at 7:52

thanks that helped
Saqib
August 16, 2010 at 18:12

Thanks dude, none of the admins here knew what to do apart from maybe reboot the machine.

All worked, I had to speficy the domian i.e.

servername.domain.net

and it conncected all fine and had two phantom sessions still open, so i logged them off and all done.

Appreciate the help.
ooty
August 25, 2010 at 12:57

Grate job man. It helped me a lot. Thanks