How to solve the problem of too many remote connection users

At work, you often need to remotely connect to the server. However, in the company, bosses and colleagues need to connect to the server, and the default maximum number of connections in the Win2003 operating system is 2, the problem is that the "Terminal Server exceeds the maximum number of connections" is often encountered, resulting in failure to log on to the server normally. The following describes several methods circulating on the Internet to solve this problem.

Recommended topics: Windows Remote Desktop applications

Solution 1: log out of the Remote Desktop instead of closing the window;

Solution 2: disconnect a user;

1. Connect to the server via telnet through various methods)

2. view the logon user list. Enter the command: query user

In this way, you can see why it comes along. It depends on your specific situation. If the user ID is 0, it is logged on locally. When the prompt is "disconnected", it indicates that the user has been disconnected and still occupies system resources and channels, in this way, the user can be kicked out. Enter the logoff ID, that is, the user with the corresponding ID is kicked.

Solution 3: restrict the time For Disconnected Sessions. recommended)

In general, it is impossible for us to stay online for a long time when maintaining a remote server. By default, the system will not be disconnected as long as we log on to the server. Therefore, we can modify this default setting to specify an automatic disconnection time.

You can set the Group Policy on the Windows 2003 Server to solve the problem: Click Start> Run and enter gpedit. msc ", press enter, open the Group Policy window, and choose computer configuration> Manage template> Windows Components> Terminal Services> sessions ", in the window on the right, double-click "set time limit for Disconnected Sessions" and set the "End disconnected session" Time to 5 minutes, or, if it is set to idle, it will be disconnected. Or open the "run" window on the remote server and enter the "tscc. msc" connection settings window. Double-click "RDP-Tcp" on the right of the "connection" item, switch to the "session" tab, and select the "substitute user settings" option, set a proper time for "End Disconnected Sessions.

Solution 4: Increase the number of connections, that is, set the maximum number of connections.

By default, the number of users allowed to connect to the remote terminal is two. We can increase the number of users simultaneously connecting to the remote terminal as needed.

Click Start> Run and enter gpedit. msc opens the Group Policy Editor window. In turn, choose computer configuration> Manage template> Windows Components> Terminal Services, and double-click "Limit connections" on the right ", set the maximum number of connections allowed by TS to a greater value.

After the above two Configuration Methods 3 & Method 4), you can basically ensure that the remote terminal connection is no longer limited. However, some people still reflect that there is only one user currently connecting, But they prompt that the maximum number of allowed connections is exceeded. Why? This is caused by improper operations. The remote desktop window is closed directly instead of being canceled when you log out from the remote desktop of the previous account. As a result, the session is not released, but is retained on the server, the number of connections is used, which affects the normal login of the next user.

Solution 5: Limit the number of user sessions

Restrict Terminal Services so that a user can connect only once. For Windows Server 2003, set "Restrict each user to only one session" Restrict each user to one session in the Terminal Services ConfigurationTerminal Services configuration) to "Yes ). In addition, you can set the "restrict end service users from using a single remote session" group policy to "enable ".

Note: different versions have different solutions!

A: This is because the maximum number of allowed connections is set in Windows 2003. After each connection, you may not log off, but close it directly. As A result, the number of connections exceeds the maximum number of connections. On Windows 2003 Server, you can set a group policy to solve the problem: Click Start> Run and enter gpedit. msc, press enter, and open the Group Policy window. Then, choose computer configuration> Manage template> Terminal Service> session ", in the window on the right, double-click "set time limit for Disconnected Sessions" and set the "End disconnected session" Time to 5 minutes. The best solution is to log out every time you disconnect the connection.

B: When many people manage the server, they must have encountered the prompt "the terminal connection has exceeded the maximum connection" when their terminal is connected to a remote computer? This is because windows2003 only supports login by two end users. When this happens, most people choose to call the data center to restart the server. However, the loss is also obvious. So what can we do? Of course there are some methods. We only need to run tsmmc on a 2003 machine. msc "to open the Remote Desktop Connection, here we add a new connection, enter the recipient's IP address account and password, then you can successfully log on to the recipient's desktop, in this case, you can start another user. To solve the problem that the number of terminal connections exceeds the maximum.

C: Start → Control Panel → change the number of connections in the authorization.