terminal server has exceeded max number of allowed connections

[yaya]

I have this message displayed for over 20 hrs. I am unable to remote connect to the server. the message i receive is "Terminal server has exceeded maximum number of allowed connection". I'm sure I haven't reached this maximum number of allowed connection. What then is the meaning of this message? Can I do something to adjust this number?

[Tino Didriksen]

You can't adjust it, unless you buy a bigger license.
Could be that some old connections aren't dying as they should.

No idea how to fix it, but to prevent it next time you can have a VNC ( http://www.realvnc.com/ ) running as a back-up login solution.

[QT]

Originally posted by yaya
Can I do something to adjust this number?

The meaning of the message is found here:

http://support.microsoft.com/default.aspx?scid=kb;IT;246109

"Error message:
The terminal server has exceeded the maximum number of allowed connections. The system cannot log you on (1B8E). Please try again or consult your system administrator.

Description: The user is attempting to log on to a Terminal Server in Remote Administration mode, but the server has reached its connection limit. Terminal Servers in Remote Administration mode allow a maximum of 2 concurrent sessions, active or disconnected."

You cannot adjust the number. You'll have to purchase more licenses. I believe the minimum number for purchase is 5. You can find out more about it here:

http://www.microsoft.com/windows2000/server/howtobuy/pricing/pricingwindows.asp#terminal

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/default.mspx

[Dubie]

Also if you can not get back in and you know no one else is useing it for anything, you could just do a rapid reboot from My ServerBeach Console.
That drops all the connections.

Peace,
Dubie

[charlie]

Originally posted by yaya
I have this message displayed for over 20 hrs. I am unable to remote connect to the server. the message i receive is "Terminal server has exceeded maximum number of allowed connection". I'm sure I haven't reached this maximum number of allowed connection. What then is the meaning of this message? Can I do something to adjust this number?

You are only allowed 2 simultaneous terminal server connections for remote management. To get back in, you'll have to request SB to "Log Off" those connections for you, or the less graceful, Rapid Reboot option.

You should go into Terminal Services Configuration and modify the properties for the RDP connection. You will want to set the proper timeouts. Keep in mind that "Logging Off" closes everything and frees the connection. "Disconnecting" such as hitting the "X" to close the Terminal Server Client or Remote Desktop Client (whichever you're using) leaves all programs running and leaves your connection as being "in use" and if your connection information hasn't changed since the last time you connected, it will re-connect you back to this session. This is great if you have long running programs that you just want to check back on once in a while.

Otherwise, make sure you set the proper options when you connect with your client in your client settings. I believe the default states that it reads the settings from the client otherwise defaults to not logging you off.

If you have something running and end up connecting to the 2nd session, then go to Terminal Services Manager and either Log Off to the other connection or Connect to it and assume that session.

charlie
=T

[knightfoo]

There is a little known feature that was introduced into the RDC 5 protocol (Windows 2003) that helps with these "too many connections" situations. There is an option that allows you to connect to the "console" from remote, which essentially gives you a 3rd RDC connection. If no one is logged into the console, it will just let you log in. If someone is logged in already and you have sufficient access (administrator) then they will be logged out and you can log in.

I would suggest only using this feature when your other two RDC connections are in use and you need to log one of them out. If you get in the habit of using the console connection then you'll just end up with 3 stuck RDC connections instead of 2 and with no way to log them out. You should still modify the timeout settings so that idle/disconnected sessions close out in a reasonable amount of time.

-knightfoo

[yaya]

Thanks, for all the information, the rapid reboot cleared everything up.

[msalo]

to access the console session, do this:

start | run - mstsc -v:0.0.0.0 /f -console
(replace the 0.0.0.0 with your ipaddress)


I use this all the time, but I use my windows server as a game server, not a web server. So i have the game's server software running at all times (doesn't run as a service.) I run that in the console session.


-Matt

[knightfoo]

Or if you're connecting from a Linux system:

# rdesktop -0 1.2.3.4

You need the latest version of rdesktop which supports the RDC protocol 5.

-knightfoo