Terminal server has exceeded maximum number of allowed connections: Solution

Generally as Terminal Client you work with desktop. But while working based on the Terminal Server environment, you may require accessing the server remotely from desktop. In this case, RDP (Remote Desktop Protocol) access is to be enabled to the server as per Microsoft package. RDP is the way to establish the connection between the Terminal Server and the Terminal Server Client. At the same time at client end RDC (Remote Desktop Connection) is getting used to make a communication with server.

But connecting to the server through remote
there is restriction- the maximum number of people can log in to the server together at the same time are only three. Here if fourth person tries to take on remote the same server at the same time it will not allow to do so. It happens also when three people have logged in together; anyone of them closed the session knowingly/unknowingly without logging off his account and again tries to log in with the same credential.
At this point of time while connecting remotely by remote desktop connection to the server, you will be displayed on the screen one pop-up message:
Terminal server has exceeded maximum number of allowed connections
So how will you log in to the server?
The resolution is at least one session needs to be killed which is inactive or not getting used by any user. To kill the session there are two ways:
1) One way is to log in to the server through console or physically with the administrator credentials and from the toolbar>right click>Task Manager>User Tab, select the inactive user, right click and log off. The session will be free and will be log in through remotely.


2) Another way is to log in remotely to any other server which is in the same workgroup of inaccessible server. Now click to start button> all programs>Administrative Tools>Terminal Services Manager window will appear. Here click the Action Tab>Connect to Computer- here you need to type the server name or IP address of the server which you are trying to access remotely. After clicking the OK button it will show the logged in user session but not getting used. Select the inactive user, right click and log off. The session will be free and will be log in through remotely.


Here you go. Now easily the server you will be able to log in through remote desktop connection which you are trying. These methods are already tested on Windows 2003 Server Operating System.