Win2003 remote login (remote desktop) maximum connection number modification method

How to modify the maximum number of remote desktop connections

1, open the Group Policy Editor window method: Click “Start”->“Run”, enter "gpedit.msc" ,“OK”. 2, in turn open “ computer configuration (computer configuration) & rarr; administrative templates (administrative templates) & rarr; windows components (windows components) & rarr; terminal services (terminal services) & rdquo; 3, double-click on the right side of the "limit number of connections ( Limit number of connections), double-click on the limit number of connections properties and select enabled to set the maximum number of connections allowed by TS maximum connections allowed to the required number. Don't forget to restart the server after making changes.

[Solution 1]

1. Find a Windows 2003 machine that can connect to the network 2. Start & ndash; Run & ndash; enter “tsmmc.msc”, jump out of a remote desktop Console 3, right click on the left side of "Remote Desktop", select "New Remote Desktop", fill in the ip, user name, password, domain name of the virtual host to be connected as required, and then click "OK" Click on the newly created remote desktop to log in to the remote virtual host. [Solution 2] Fault details: When logging in to the terminal server with a remote desktop link, you will often encounter "The terminal server exceeds the maximum number of allowed links". Such an error causes the terminal server to be unable to log in properly. The reason for this problem is that the default number of links for Terminal Services is 2 links, and if you log in to the remote desktop without logging out, instead of directly closing the remote desktop window, then the actual The upper session is not released, but remains on the server side, which will take up the total number of links. When this number reaches the maximum allowable value, the failure prompt that cannot be connected as shown in Figure 2-1 will appear. Figure 2-1 Solution: 1. Local computer, in order: Start ==> Run ==> Input: mstsc /admin As shown in Figure 2-2: Figure 2-2 2. After input is complete, click OK to enter After the carriage return, see the familiar remote desktop connection window, as shown in Figure 2-3. Then enter the user name and password required for the remote, click the connection, and log in again, you can force the login to the 0 user of the server by default. Figure 2-3 OK. Solved! Note: Of course, you can also directly restart the server to solve the problem, but do not advocate! [Sweeping work] 1, after logging in to the remote virtual host, open the "Task Manager", select "User", kick off those 2 users who stay in the system 2, start-run-gpedit.msc-computer configuration-management template-windows component-terminal service-session, right window select "disconnected" Session setting time limit”-Selection is enabled, set a time win2K/win2003 terminal server exceeds the maximum number of allowed connections. 1. Log out to remote desktop instead of directly closing the window. 2. Limit the existence time of the disconnected session. 1. Modify Run-Tscc.msc (Terminal Service Configuration) from the Terminal Services Configuration - Connection - Double click RDP-Tcp or right click - Properties - Session - Select the first alternate user setting (O) - End disconnected Session [change the default value "never" to an appropriate time, such as 30 minutes] 2. Start with group policy modification - run -gpedit.msc - computer configuration - Rational template - windows component - terminal service - session right window select to set time limit for disconnected session - select is enabled, select a time three, increase the maximum number of links 1, modify from the terminal service configuration: run -Tscc.msc ( Terminal Services Configuration) - Connection - Double click RDP-Tcp or right click - Properties, select "Network Card" tab - Modify "Maximum Connections" to change the value you want, 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 up, first look at the user who logged in: Enter the command: query user System returns: C:>query user At this point you may see that the difference may be different, depending on the specific circumstances. To find out who is disconnected but still occupies system resources and channels, 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 solution is basically useless. Later, when I used the server terminal server to exceed the maximum allowable number of connections, I used to consider using a cold boot server, but this must run a computer room. The best way I found recently is In the "Run" command line, type: mstsc /console /v: your server IP: remote port

author CAMYD