window2003 Remote Desktop "reached maximum number of connections"

window2003 Remote Desktop "reached maximum number of connections"

The remote Desktop is used to manage the windows2003 server, and the maximum connections reached prompt is not available to log in to the Remote Desktop. The reason for this hint is that the window was closed directly when using Remote Desktop instead of the "logoff" user, causing the Remote Desktop window to be closed, but the resource used by the user was not released, reaching the maximum number of connections allowed by the system.

Workaround:
1. Forcing a remote connection to the server
In the Run window, enter MSTSC/V:XXX.XXX.XXX.XXX (here is server IP)/console. You can force log on to the remote server.

2. Log off the disconnected user.
Go to the console:
Enter the query user command to record the ID of the logged in users
Log off logged-in user with logoff Id command

3. Ways to resolve this problem
Use Logoff to exit Remote Desktop instead of closing the window directly
Limit the time that a disconnected session exists by running a-tscc.msc-connection-double-click Rdp-tcp or right-click-Properties-session-Select the first alternative user setting (O)-end a disconnected session (change the default value from "Never" to an appropriate time, such as 30 minutes)
Method One: Use "logout" to exit the remote desktop instead of closing the window directly
Law two: Kick out a disconnected user
1, first telnet to this host (no matter what method you use), of course, if you can directly operate the machine better, but direct operation will not have to use command line, with the console more intuitive (skip).
2, Telnet up, first look at the user login:
Input command: Query user system returns:

User name username session name sessions, name ID status, state idle time, logon hours, logon time
Administrator Console 0 is in operation. 2007-1-12 10:24
Lucy 1 record No 2007-1-12 10:35
>administrator rdp-tcp#35 2 is disconnected. 2007-1-25 18:09

At this point it may be different from mine, depending on your specific situation.
The user of ID 0 is logged on locally
ID 1 and ID 2 are 3389 logged users, the former in operation, the latter has been disconnected, but disconnected still occupy the system resources and channels, we have to kick it off, such as under the operation.
Input command: Logoff 1

Look again.

C:\Documents and Settings\administrator.ad>query User
User name username session name sessions, name ID status, state idle time, logon hours, logon time
Administrator Console 0 is in operation. 2007-1-12 10:24
>administrator rdp-tcp#35 2 is disconnected. 2007-1-25 18:09

3, if the server shuts down the Telnet function (this is the default), but also through SQL Server xp_cmdshell extended stored procedures, using the format: Master.dbo.xp_cmdshell "" Command content ", the rest can refer to the second step. This method requires permission to access xp_cmdshell.

Law III (Best Practices-recommended): Limit the time that a disconnected session exists
In general, when we maintain a remote server, it is not possible to be online for a long time, but the system defaults to no longer disconnect as long as it is logged in. Therefore, we can modify this default setting to give it an auto-disconnect time.
You can resolve the issue by setting it up in Group Policy on a Windows 2003 server: Click start → run, enter gpedit.msc, open the Group Policy window after carriage return, and then navigate to computer Configuration → administrative Templates →windows components → Terminal Services → sessions. Then, in the right-hand window, double-click Set time limit for disconnected sessions, set the end disconnected session time to 5 minutes in the window that opens, or disconnect when set to idle.
Or
Open the Run window on the remote server and enter the TSCC.msc Connection Settings window. Then double-click the "Rdp-tcp" to the right of the "connections" item, switch to the "Sessions" tab, select the "Override user Settings" option, and then set an appropriate time for "end disconnected session".

Law IV: Increase the number of connections, that is, set the number of connections can be more
By default, the number of remote terminal connections allowed is 2 users, and we can increase the number of users who are connected to the remote connection as appropriate.
Click start → run, enter gpedit.msc to open the Group Policy Editor window, navigate to Computer Configuration → administrative Templates →windows components → Terminal Services, and double-click the limit number of connections on the right to set the maximum number of connections that TS allows.

With the above two configurations (Law III & IV), it is basically possible to ensure that remote terminals are no longer restricted when connected. However, it is still reflected that the current simultaneous only one user to connect, but prompted to exceed the maximum allowable number of links, what is the reason? This happens due to improper operation. When the previous account logged on to the Remote Desktop and exited without logging off, instead of shutting down the Remote Desktop window directly, the session was not released, but continued to remain on the server side, consuming the number of connections, which would affect the next user's normal login.

Method Five: Limit the number of user sessions
Restrict Terminal Services so that a user can only connect once
For Windows Server 2003, in Terminal Services configuration (Terminal Services config), "Restrict per user to only one session" (Restrict One session) is set to Yes (yes). Additionally, you can set the Restrict Terminal Services users to use a single remote session Group Policy to Enabled.

There are different ways to resolve a version:
A: This is because Windows 2003 sets the maximum allowed connections limit, and you may not log off each time you connect, but it shuts down directly, causing the number of connections to exceed the maximum number of connections. You can fix the problem by setting it up in Group Policy on a Windows 2003 server: Click start → run, enter gpedit.msc, open the Group Policy window after you enter, and then navigate to computer configuration → administrative templates → Terminal Services → sessions, and then in the right window, double-click Set the time limit for disconnected sessions to set the end disconnected session time to 5 minutes in an open window. The best solution is the way you log off each time you disconnect.

B: Often many people manage the server's friends must have encountered too much of their terminal connection to the remote computer when the "terminal connection exceeded the maximum connection" prompt it?
This is because windows2003 only supports 2 end-user logins. When this happens, most people choose to call the computer room to restart the server. But the damage is obvious. So what can we do to fix it? Method of course there is. We only need to run "Tsmmc.msc" on a 2003 machine to open the Remote Desktop Connection, where we add a new connection, enter the other's IP address account number and password can be successfully landed on the other side of the desktop, then the next user can be kicked. You can solve the problem of exceeding the maximum number of terminal connections.

C: Start-Control Panel---Authorization to change the number of connections

Source Address: http://space.itpub.net/10067101/viewspace-614747

window2003 Remote Desktop has reached the maximum number of connections