Win2003 Telnet Maximum Connection number how to modify

Win2003 Telnet Maximum connection number how to modify

Ways 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, turn on the Computer configuration (computer configuration) → Administrative Templates (Administrative Templates) →windows components (Windows components) → Terminal Services (terminal Services) "

3, double-click the Limit number of connections (limit count of connections) on the right, and then double-click the Open Configuration window (limit # of Connections properties) to select enabled to associate its TS maximum The maximum number of connections allowed by the connections allowed is set to the required quantity.

Don't forget to reboot the server when you modify it.

"Workaround 1"

1. Find a windows2003 machine that can connect to the network

2. Start – Run – Enter "Tsmmc.msc" and jump out of a remote Desktop console

3, right click on the left "Remote Desktop", select "New Remote Desktop", in accordance with the requirements of the virtual host to connect the IP, user name, password, domain name, and then click "OK"

4, click on a new good Remote Desktop, you can log into the remote virtual host

"Workaround 2"

Failure details: When you log on to a terminal server with a Remote Desktop link, you often experience a terminal server exceeding the maximum number of allowed links. Such errors cause the Terminal Server to not log on correctly. This problem is caused by the fact that the default number of links to Terminal Services is 2 links, and that when you log on to Remote Desktop instead of logging off, instead of simply shutting down the Remote Desktop window, the session is not released, but continues to remain on the server side, This takes up the total number of links, and when this number reaches the maximum allowable value, a failure hint that cannot be connected as shown in Figure 2-1 appears.

Figure 2-1

Solution: 1, the local computer, in turn: Start ==> run ==> input: Mstsc/admin as shown in Figure 2-2:

Figure 2-2

2, after the completion of the input click to determine carriage return, enter, see the Familiar Remote Desktop Connection window, as shown in Figure 2-3. And then enter the remote required username and password, click on the connection, the landing, you can force the default landing to the server under the 0 users.

Figure 2-3

OK, it's settled! Note: Of course, you can also directly restart the server to solve the problem, but do not advocate!

"Cleanup Work"

1, after landing to the remote virtual host, open "Task Manager", select "User", kick off the 2 left in the system users

2. Start-run-gpedit.msc-Computer Configuration-Administrative Templates-windows components-Terminal Services-sessions, right window select "Set time limit for disconnected sessions"-select enabled, set a time

WIN2K/WIN2003 Terminal Server exceeds maximum allowable number of connections

Logout to exit the remote desktop instead of closing the window directly

Second, limit the time that a disconnected session exists

1. Modify from Terminal Services Configuration

Run-tscc.msc (Terminal Services Configuration)-Connect-double-click Rdp-tcp or right-click-Properties-session-Select the first alternate user setting (O)-end a 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-Administrative Templates-windows components-Terminal Services-Session right window select Set time limit for disconnected sessions-select enabled, select a time

Third, increase the maximum number of links

1. Modify from Terminal Services Configuration: Run-tscc.msc (Terminal Services Configuration)-Connect-double-click Rdp-tcp or right-click-Properties, select the "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 occupy more system resources. However, the modified value here does not seem to work, set to unlimited time will still appear in this article said.

2. The Group Policy level is higher than the Terminal Services configuration, and the corresponding options in the Terminal Services configuration are grayed out when Group Policy is enabled

Run-gpedit.msc-Computer Configuration-Administrative Templates-windows components-Terminal Services Double-click the limit number of connections to the right-select enabled-fill in the maximum number of connections allowed

Iv. changing the remote terminal mode

Open the Control Panel, double-click Add Remove Program, add remove Windows Components, components, select Terminal Services in the Windows Components Wizard dialog box, next, Application Server, Next, and then follow the prompts to change the mode of Terminal Services.

Windows 2000 Terminal Services has 2 modes of Operation: Remote Administration mode and Application Server mode. Remote Administration mode allows the system administrator to remotely administer the server and allows only 2 terminal sessions to log on to the Terminal server at the same time. Application Server mode allows users to run more than one application, allowing multiple users to log on to the server from the terminal. However, users who apply Terminal Services must have Terminal Services Licensing, which means that a Terminal Services Licensing server must be set up in this domain or workgroup within 90 days, otherwise the user will need to remove the application and then reinstall it.

V. Modify the Local Security policy

Control Panel >> Administration Tools >> Local Security Policy >> Local policy >> security options >>

1, first find the >>microsoft network server: The idle time required before suspending the session defaults to: 15 minutes, to the time of their own (that is, after landing no action idle more than how much time after automatic disconnect)

2, then find >> Network security: Force logoff after logon hours. The default is: Disabled, be sure to change to: Enabled

If a workaround 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 better, but the direct operation does not need to use the command line, which of course, know the machine Super Administrator password, you can use Opentelnet to open the remote server telnet port.

2, Telnet up, first look at the landing of the user:

Enter command: Query user

System return:

C:>query User

At this point can be seen may be different, according to the specific circumstances. Find users who are disconnected but still occupy system resources and channels, and we'll kick it off. As the following operation can be.

Input command: Logoff 1

3. If the server turns off Telnet (which is the default), you can also extend the stored procedure through SQL Server xp_cmdshell, 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 no use later I use the server Terminal Server exceeded the maximum allowable number of connections, previously considered to use cold start the server, but this must run a trip to the engine room, recently issued

Now the best way is to enter in the "Run" command line: mstsc/console/v: Your server IP: remote port