Common solutions for remotely exceeding the maximum number of connections on the server

 

This problem is caused by the absence of two links in the terminal service. If you log on to the Remote Desktop, you can directly close the remote desktop window instead of logout, in fact, the session is not released, but is retained on the server. This will occupy the total number of connections. When the maximum number is reached, the above prompt will appear.
This problem is caused by the absence of two links in the terminal service. If you log on to the Remote Desktop, you can directly close the remote desktop window instead of logout, in fact, the session is not released, but is retained on the server. This will occupy the total number of connections. When the maximum number is reached, the above prompt will appear.

How to avoid it?
1. log out of the Remote Desktop instead of closing the window directly.
2. Restrict the time For Disconnected Sessions
1. Modify from terminal service configuration
Run-TSCC. MSC (terminal service configuration)-connection-double-click RDP-TCP or right-click-properties-session-select the first replacement user setting (o) -end a disconnected session [change the default value "never" to an appropriate time, for example, 30 minutes]

2. Modify the slave Group Policy
Start-run-gpedit. MSC-Computer Configuration-management template-Windows Components-Terminal Services-session
In the window on the right, set the time limit for Disconnected Sessions-select Enabled and select a time
3. Increase the maximum number of links
1. Modify from terminal service configuration: Run-TSCC. MSC (terminal service configuration)-connection-double-click RDP-TCP or right-click-properties, select the "Nic" tab-change "Max connections" to your desired value, of course, this value cannot be too large, otherwise it will occupy a large amount of system resources. However, the modified value does not seem to work here. When it is set to no limit, the situation described in this article will still appear.

2. The group policy level is higher than the terminal service configuration. When the Group Policy is enabled, the corresponding options in the terminal service configuration become gray and unchangeable.
Run-gpedit. MSC-Computer Configuration-management template-Windows Components-Terminal Service
Double-click "Limit connections" on the right, select "enabled", and enter the maximum number of connections allowed.
4. Change the Remote Terminal Mode
Open "Control Panel", double-click "add and delete program", click "add and delete Windows components", and select "Terminal Service" in the Windows component wizard dialog box ", "Next", "Application Server", and "Next", and then follow the prompts to change the terminal service mode.

Windows 2000 Terminal Services have two operating modes: Remote Management Mode and Application Server mode. The remote management mode allows the system administrator to remotely manage the server, and allows only two terminal sessions to log on to the terminal server at the same time. The Application Server mode allows you to run more than one application and allow multiple users to log on to the server from the terminal. However, the application terminal service user must have terminal service authorization, that is, the terminal service authorization server must be set in this domain or working group within 90 days. Otherwise, the user must delete the application, then reinstall.

5. modify local security policies
Control Panel> Administrative Tools> Local Security Policies> Local Policies> Security Options>
1. First find> Microsoft network server: The Idle Time Required Before the session is suspended
The default value is 15 minutes, which is changed to the time required by the user (that is, the user is automatically disconnected after no action is idle after login)
2. Find> Network Security: log out after the logon time is exceeded. The default value is disabled. Make sure to change to: enabled.

If a solution already exists:
1. First, you can telnet to the host (no matter which method you use). Of course, it is better to operate the machine directly, but you do not need to use the command line for direct operations, if you know the password of the Super administrator, you can use opentelnet to open the telnet port of the remote server.
2. After telnet, check the login user first:
Enter the command: Query user
System return:
C:> query user
Username sessionname ID state idle time Logon Time
K12update console 1 running
At this time, we can see that the possible differences are different, depending on the specific situation.
Users with ID 0 are locally logged on, and users with ID 1 and ID 12 are 3389 logged on. The former is running, and the latter is disconnected, however, if it is disconnected, it still occupies system resources and channels. We need to kill it. Perform the following operations.

Enter the command: logoff 1
3. If the Telnet function is disabled on the server (this is the default one), you can also extend the stored procedure through SQL Server's xp_cmdshell. The format is master. DBO. xp_cmdshell 'COMMAND content'. For more information, see Step 2. This method requires the permission to access xp_mongoshell.

The above method is basically useless.