Remote desktop exceeding the maximum number of connections
- 2020-05-06 12:01:43
- OfStack
[system environment]
system: Windows 2003
has many ways to solve this problem. If you need to log in the server immediately, easy's best way is
[solution]
1. Find a networked windows2003 machine,
Enter "tsmmc.msc", and then a remote desktop console
will pop up 3. Right click the "remote desktop" on the left, select "new remote desktop", fill in ip, username, password, domain name of the virtual host to be connected as required, and then click "ok"
4, click the new remote desktop, you can login to the remote virtual host
1. After logging in to the remote virtual host, open the "task manager", select "user", and kick the two remaining users
Start - run -gpedit.msc- computer configuration - management template -windows components - terminal services - session, the right window select "set a time limit for disconnected sessions" - select enabled, set a time
Problem with win2K/win2003 terminal server exceeding the maximum number of connections allowed
Use logout to exit the remote desktop instead of closing the window
2. Limit the duration of a disconnected session to
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 alternate user setting (O)- end the disconnected session [change the default value from "never" to an appropriate time, such as 30 minutes]
2. Modify
from group policy Start - run -gpedit.msc- computer configuration - management template -windows component - terminal services - session right window select set time limit for disconnected session - select enabled, select a time
3. Increase the maximum number of links
1, from the terminal service configuration: run -Tscc.msc(terminal service configuration)- connect - double click RDP-Tcp or right click - property, select the "network card" TAB - change the "maximum number of connections" to the value you want, of course, this value can not be too large, otherwise it will take up more system resources. However, the modified values here don't seem to work, and if you set them to unlimited, you'll still have the situation described in this article.
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 grey and cannot be modified
Run - gpedit.msc - computer configuration - management template -Windows component - terminal service double-click on the right "limit connections - select enabled" - fill in the maximum number of connections allowed
4. Change the remote terminal mode
opens "control panel", double-click "add delete program", click "add delete Windows component", "component", in the Windows component wizard dialog box, select "terminal service", "next", "application server", "next", and then follow the prompts to change the mode of terminal service.
Windows 2000 terminal services run in two modes: remote administration and application server. The remote administration mode allows the system administrator to remotely manage the server and only allow two terminal sessions to log on 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 from the terminal to access the server. However, the user of the application terminal service must have the terminal service authorization, that is, must set up the terminal service authorization server in this domain or workgroup within 90 days, otherwise the user needs to delete the application and then reinstall it.
Modify the local security policy
Control panel > > Management tool > > Local security policy > > Local policy > > Security options > >
1. Find > first > Microsoft web server: the default amount of idle time required before a session is suspended is 15 minutes. This is changed to the amount of time you need (that is, the number of idle hours after you log in without any action) 2. Then find > > Network security: force logout after login time. The default is: disabled, be sure to change to:
enabled If a solution has occurred:
1, you can first of all telnet to this host (whichever method you use), of course, if you can directly operate the machine is better, but direct operation does not need to use the command line, that is, of course, knowing the password of the machine super administrator, you can use OpenTelnet to open the remote server Telnet port.
2. After going up to Telnet, check the logged-in user:
Enter the command: query user
The system returns:
C: > query user
At this time can see may not be the same, according to the specific situation. Find out who is disconnected but still using system resources and channels, and we'll kick it out. The following operation can be done.
Enter the command: logoff 1
3. If the server turns off telnet (which is the default), the stored procedure can also be extended by xp_cmdshell of SqlServer in the format master.dbo.xp_cmdshell '
Command the contents' and refer to step 2 for the rest. This approach requires access to xp_cmdshell,
The above solution was basically useless. Later, when I used the server terminal server to exceed the maximum number of connections allowed, I used to consider using the cold startup server. However, I had to go to the machine room and recently sent
The best way to do this is to type mstsc /console /v: your server IP: remote port
in the run command line
Or use the following 3389 to connect to the client enhanced windows terminal connector enhanced (to solve the problem of too many terminals)
system: Windows 2003
has many ways to solve this problem. If you need to log in the server immediately, easy's best way is
Start - input while running :mstsc /console /v:192.168.12.241:3389
[solution]
1. Find a networked windows2003 machine,
Enter "tsmmc.msc", and then a remote desktop console
will pop up 3. Right click the "remote desktop" on the left, select "new remote desktop", fill in ip, username, password, domain name of the virtual host to be connected as required, and then click "ok"
4, click the new remote desktop, you can login to the remote virtual host
1. After logging in to the remote virtual host, open the "task manager", select "user", and kick the two remaining users
Start - run -gpedit.msc- computer configuration - management template -windows components - terminal services - session, the right window select "set a time limit for disconnected sessions" - select enabled, set a time
Problem with win2K/win2003 terminal server exceeding the maximum number of connections allowed
Use logout to exit the remote desktop instead of closing the window
2. Limit the duration of a disconnected session to
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 alternate user setting (O)- end the disconnected session [change the default value from "never" to an appropriate time, such as 30 minutes]
2. Modify
from group policy Start - run -gpedit.msc- computer configuration - management template -windows component - terminal services - session right window select set time limit for disconnected session - select enabled, select a time
3. Increase the maximum number of links
1, from the terminal service configuration: run -Tscc.msc(terminal service configuration)- connect - double click RDP-Tcp or right click - property, select the "network card" TAB - change the "maximum number of connections" to the value you want, of course, this value can not be too large, otherwise it will take up more system resources. However, the modified values here don't seem to work, and if you set them to unlimited, you'll still have the situation described in this article.
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 grey and cannot be modified
Run - gpedit.msc - computer configuration - management template -Windows component - terminal service double-click on the right "limit connections - select enabled" - fill in the maximum number of connections allowed
4. Change the remote terminal mode
opens "control panel", double-click "add delete program", click "add delete Windows component", "component", in the Windows component wizard dialog box, select "terminal service", "next", "application server", "next", and then follow the prompts to change the mode of terminal service.
Windows 2000 terminal services run in two modes: remote administration and application server. The remote administration mode allows the system administrator to remotely manage the server and only allow two terminal sessions to log on 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 from the terminal to access the server. However, the user of the application terminal service must have the terminal service authorization, that is, must set up the terminal service authorization server in this domain or workgroup within 90 days, otherwise the user needs to delete the application and then reinstall it.
Modify the local security policy
Control panel > > Management tool > > Local security policy > > Local policy > > Security options > >
1. Find > first > Microsoft web server: the default amount of idle time required before a session is suspended is 15 minutes. This is changed to the amount of time you need (that is, the number of idle hours after you log in without any action) 2. Then find > > Network security: force logout after login time. The default is: disabled, be sure to change to:
enabled If a solution has occurred:
1, you can first of all telnet to this host (whichever method you use), of course, if you can directly operate the machine is better, but direct operation does not need to use the command line, that is, of course, knowing the password of the machine super administrator, you can use OpenTelnet to open the remote server Telnet port.
2. After going up to Telnet, check the logged-in user:
Enter the command: query user
The system returns:
C: > query user
At this time can see may not be the same, according to the specific situation. Find out who is disconnected but still using system resources and channels, and we'll kick it out. The following operation can be done.
Enter the command: logoff 1
3. If the server turns off telnet (which is the default), the stored procedure can also be extended by xp_cmdshell of SqlServer in the format master.dbo.xp_cmdshell '
Command the contents' and refer to step 2 for the rest. This approach requires access to xp_cmdshell,
The above solution was basically useless. Later, when I used the server terminal server to exceed the maximum number of connections allowed, I used to consider using the cold startup server. However, I had to go to the machine room and recently sent
The best way to do this is to type mstsc /console /v: your server IP: remote port
in the run command line
Or use the following 3389 to connect to the client enhanced windows terminal connector enhanced (to solve the problem of too many terminals)