The server remote exceeds the maximum number of connections. Common solution

causes the problem because the default number of links for Terminal Services is 2 links, and if you log in to the remote desktop, if you do not log out, you can directly close the remote desktop. Window, then the session is not actually released, but remains on the server side, which will take up the total number of links, the above prompt will appear when the number reaches the maximum allowable value. How to avoid? 1. Log out of the remote desktop instead of closing the window directly. 2. Limit the existence of the disconnected session. 1. Modify the running from the terminal service configuration. -Tscc.msc (Terminal Service Configuration) - Connection - Double click RDP-Tcp or Right-click - Properties - Session - Select the first alternate user setting (O) - End the disconnected session [Change the default value "never" to an appropriate time, such as 30 minutes] 2. From the group Policy modification start-run-gpedit.msc-computer configuration-management template-windows component-terminal service-session right window select time limit for disconnected session-selection is enabled, select one time three, increase the maximum number of links Modify from Terminal Services Configuration: Run -Tscc.msc (Terminal Service Configuration) - Connection - Double click RDP-Tcp or right click - Properties, select & ldquo; NIC & rdquo; tab - modify & ldquo; maximum number of connections & rdquo; change to you The required value, of course, this value can not be too large, otherwise it will take up more system resources. However, the value modified here does not seem to work. If it is set to unlimited, 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 option in the terminal service configuration will be grayed out and cannot be modified to run -gpedit.msc - computer configuration - management template - Windows component - terminal service double click on the right & rdquo; limit the number of connections <; select & rdquo; is enabled & ldquo; - fill in the maximum number of connections allowed four, change the remote terminal mode to open "control panel", double-click "add delete program", click “ Add Remove Windows Components >, "Components", select “Terminal Services> in the Windows Components Wizard dialog box, “Next”,“Application Server",>;Next”, then Follow the prompts to change the mode of Terminal Services. Windows 2000 Terminal Services has two modes of operation: 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 in to the terminal server at the same time. The application server mode allows users to run more than one application, allowing multiple users to log in to access the server from the terminal. However, users of Terminal Services must have Terminal Services Licensing, that is, the Terminal Services Licensing Server must be set up in this domain or workgroup within 90 days, otherwise the user will need to delete the application and then reinstall it. V. Modify Local Security Policy Control Panel >>Management Tools>>Local Security Policy>>Local Policies>>Security Options>>>>>>>>>> The idle time required to suspend the session defaults to: 15 minutes, instead of the time you need (that is, after the login, no action is idle, how much time is automatically disconnected) 2. Then find >> network security: over Force logout after login time. The default is: disabled, must be changed to: Enabled If a solution has occurred: 1. First you can telnet to this host (no matter which method you use), of course, if you can directly operate the machine, but directly You don't have to use the command line. Of course, if you know the password of the super administrator of the machine, you can use OpenTelnet to open the Telnet port of the remote server. 2. After Telnet, first look at the logged in user: Enter the command: query user System returns: C:>query user USERNAME SESSIONNAME ID STATE IDLE TIME LOGON TIME k12update console 1 Running 2007-3-14 14:57 At this time It may be different, depending on the circumstances. The ID 0 user is locally logged in. ID 1 and ID 12 are 3389 login users. The former is running, the latter is disconnected, but the system resources and channels are still occupied, and we have to kick it off. Just do the following. Enter the command: logoff 1 3. If the server has turned off the telnet function (this is the default), you can also extend the stored procedure through the xp_cmdshell of SqlServer, using the format: master.dbo.xp_cmdshell 'command content', and the rest can refer to the second step. This method requires permission to access xp_cmdshell. The above method is basically useless