How to modify the maximum number of connections for remote desktop
1 open the group policy editor window
Method: Click \u0026ldquo;Start\u0026rdquo;-\u0026gt;\u0026ldquo;Run\u0026rdquo; enter \u0026quot;gpedit.msc\u0026quot; \u0026ldquo;OK\u0026rdquo;.
2 open \u0026ldquo;computer configuration\u0026rarr;administrative templates\u0026rarr;windows components\u0026rarr;terminal services\u0026rdquo;
3. Double-click the 'limit number of connections' on the right then double-click to open the configuration window (limit number of connections properties) select enabled and set the maximum number of connections allowed by TS maximum connections allowed to the required The quantity is sufficient.
Don't forget to restart the server after modification.
1. Find a Windows2003 machine that can connect to the Internet.
2. Start \u0026ndash;Run\u0026ndash;Enter \u0026ldquo;tsmmc.msc\u0026rdquo ; a remote desktop console pops up
3. Right-click on the 'Remote Desktop' on the left select 'New Remote Desktop' and fill in the ip user name password of the virtual host to be connected as required Domain name and then click \u0026ldquo;OK\u0026rdquo;
4 click on the newly created remote desktop you can log in to the remote virtual host
Fault details: When logging in to the terminal server with a remote desktop link you often encounter 'terminal server exceeds the maximum allowable number of links'. Errors such as this result in the failure to log in to the terminal server normally. The reason for this problem is that the default number of links in the terminal service is 2 links and when logging in to the remote desktop if you log in to the remote desktop instead of logging out you can directly close the remote desktop window. The upper session is not released but continues to remain on the server side which will occupy the total number of links. When this number reaches the maximum allowable value there will be a connection failure prompt as shown in Figure 2-1.
Solution: 1. Local computer in turn: Start ==> Run ==> Enter: mstsc /admin as shown in Figure 2-2:
2. After the input is complete click OK to enter and then enter After the car you will 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 connect and log in again you can force login to the server's 0 user by default.
OK. Solved! Note: Of course you can directly restart the server to solve the problem but it is not recommended !
1. After logging in to the remote virtual host open the 'Task Manager' select 'User' and kick that 2 A user left in the system
2 start-run-gpedit.msc-computer configuration-administrative template-windows component-terminal service-session select “set time limit for disconnected session” in the right window －Select Enabled set a time
The problem that the win2K/win2003 terminal server exceeds the maximum allowable number of connections
1. Use logout to exit the remote desktop instead of closing the window directly
2 Restrict the existence time of disconnected sessions
1. Modify from the terminal service configuration
Run-Tscc.msc (terminal service configuration)-connect-double click RDP-Tcp or right click-properties-session －Select the first alternative user setting (O)－End the disconnected session [change the default value \u0026ldquo;never\u0026rdquo; to an appropriate time such as 30 minutes]
2 modify from the group policy
Start-Run-gpedit.msc-Computer Configuration-Administrative Templates-Windows Components-Terminal Services-Sessions on the right side of the window choose to set time limits for disconnected sessions-choose Enabled choose a time
3. Increase the maximum number of links
1. Modify from the terminal service configuration: run-Tscc.msc (terminal service configuration)-connection-double-click RDP-Tcp or right-click-properties select 'network card' Tab-modify the 'maximum number of connections' to the value you need of course this value can not be too large otherwise it will take up more system resources. However the modified value here does not seem to work and the situation described in this article will still occur when set to unlimited.
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 will become gray and cannot be modified.
Run-gpedit.msc-computer configuration-management template- Windows Components-Terminal Services Double-click on the right 'Limit the number of connections'-select 'Enabled'-fill in the maximum number of connections allowed
Four. Change the remote terminal mode
Open the 'Control Panel' \u0026rdquo; double-click \u0026ldquo;Add Remove Programs\u0026rdquo; click \u0026ldquo;Add Remove Windows Components\u0026rdquo;\u0026ldquo;Components\u0026rdquo; select \u0026ldquo;Terminal Services\u0026rdquo; \u0026ldquo;Next\u0026rdquo; in the Windows Components Wizard dialog box \u0026ldquo;Application server\u0026rdquo;\u0026ldquo;Next\u0026rdquo; and then follow the prompts to change the terminal service mode.
Windows 2000 Terminal Services has two operating modes: remote management mode and application server mode. The remote management mode allows the system administrator to remotely manage the server and only allows 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 who apply Terminal Services must have Terminal Services authorization that is a Terminal Services authorization server must be set up in this domain or workgroup within 90 days otherwise the user must delete the application and then reinstall it.
Five. Modify the local security policy
Control Panel\u0026gt;\u0026gt;Management Tools\u0026gt;\u0026gt;Local Security Policy\u0026gt;\u0026gt;Local Policy\u0026gt;\u0026gt;Security Options\u0026gt;\u0026gt;
1 First find> Microsoft network server: The idle time required before suspending the session is 15 minutes by default and change to the time you need (that is automatically disconnect after logging in for more than how long idle without action) < br/>2. Then find> Network Security: Force logout after the login time has elapsed. The default is: disabled must be changed to: enabled
If the solution has occurred:
1 first you can telnet to this host (no matter which method you use) of course if you can directly It is better to operate the machine but you do not need to use the command line for direct operation. Of course you can use OpenTelnet to open the Telnet port of the remote server if you know the password of the super administrator of the machine.
2. After Telnet goes up look at the logged-in user first:
Enter the command: query user
The system returns:
What can be seen at this time may be different depending on the specific situation. Find out users who are disconnected but still occupy system resources and channels. We need to kick them out. Just proceed as follows.
Enter the command: logoff 1
3. If the server turns 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' 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 use the server terminal server to exceed the maximum allowable number of connections I used to consider cold-starting the server but this must be done in the computer room. I recently posted< br/>The best way is to enter in the 'Run' command line: mstsc /console /v: your server IP: remote port
Author CAMYD?win2008 IIS7 installation tutorial-Computer Knowledge Network