How to solve the problem that the Server Remote Desktop exceeds the maximum number of connections

This article introduces a variety of methods to tell you how to solve the problem that the Server Remote Desktop exceeds the maximum number of connections. If you encounter such problems, refer to it.

[Solution]
1. Find a windows2003 machine that can be connected to the network
2. Start-run-Enter "tsmmc. msc" to jump out of a remote desktop console.
3. Right-click "Remote Desktop" on the left, select "New Remote Desktop", enter the ip address, user name, password, and domain name of the VM to be connected as required, and then click "OK"
4. Click the new remote desktop to log on to the remote VM.
[Tail scanning]
1. log on to the remote virtual host, open "Task Manager", select "user", and kill the two users that are in the system.
2. Start-run-gpedit. msc-Computer Configuration-management template-windows Components-Terminal Services-session, select "set time limit for Disconnected Sessions" in the right window, select Enabled, and set a time
Win2K/win2003 Terminal Server exceeds the maximum number of connections allowed
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-right-side window of Session select set time limit for Disconnected Sessions-select Enabled, 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"-select "enabled"-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 default Idle Time Required Before the session is suspended is 15 minutes, change to the time needed by yourself (that is, automatic disconnection 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

At this time, we can see that the possible differences are different, depending on the specific situation. Find out the user who is disconnected but still occupying 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_mongoshell in the format of master. dbo. xp_mongoshell'
Command content '. For more information, see Step 2. This method requires the permission to access xp_mongoshell.
The above solution is basically useless. When I used the Server Terminal Server to exceed the maximum number of allowed connections, I used to consider using a cold start server. But in this case, I had to go to the IDC.
The best way is to enter mstsc/console/v: Your Server IP Address: Remote port in the "run" command line.