Five steps to solve the "server exceeded the maximum allowed connections" error

Frequent remote login to the server these days, due to lack of timely logout or other circumstances, the system prompts when logging in again in the morning: "The terminal server exceeds the maximum number of allowed connections."

There are many ways to solve this phenomenon. If you need to log in to the server right away, the easiest way is:

Start-Run-mstsc /console /v: Server Name or IP or Domain Name: Remote Port:

For example: mstsc /console /v:222.222.215.222:3389

Cause: 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." "This type of error causes the terminal server to fail to log in properly. The cause of the problem is that the default number of links for Terminal Services is 2 links, and if you log out of the remote desktop without logging out, but close the remote desktop window directly, then In fact, the session is not released, but remains on the server side, which will take up the total number of links. When the number reaches the maximum allowable value, the above prompt will appear.

Five Steps to Avoid Landing Errors

1. Log out of the remote desktop instead of closing the window directly

Open the Control Panel and double-click Add and Remove Programs. Click "Add and remove Windows components", "Components", select "Terminal Services", "Next", "Application Server", "Next" in the Windows Component Wizard dialog box, and 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.

Second, limit the disconnected session existence time

1, modify from the terminal service configuration

Run-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] < Br>

2, from group policy modification

start-run-gpedit.msc-computer configuration-management template-windows component-terminal service-session

right window is selected as disconnected Session setting time limit - select is enabled, select a time

3. Increase the maximum number of links

1. Modify from Terminal Services Configuration: Run -Tscc.msc (Terminal Service Configuration) -Connection - Double click RDP-Tcp or right click - Properties, select "Network Card" tab - Modify "Maximum Connections" to change to the value you need, of course, this value can not be too large, otherwise it will occupy more systems. 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 options in the terminal service configuration will be grayed out.

Run-gpedit.msc-Computer Configuration - Administrative Templates - Windows Components - Terminal Services

Double-click "Restricted Connections" on the right - select "Enabled" - Fill in the maximum number of connections allowed

4. Change the remote terminal mode < Br>

Recommended use:

Start-Administrative Tools-Terminal Service Configuration-Server Configuration-Restrict each user to use one session

V. Modify Local Security Policy

Control Panel > Administrative Tools > Local Security Policy Local Policies > Security Options

1. First find "Microsoft Web Server: Free time required before suspending a session

Default is : 15 minutes, change to the time you need (that is, after the login, no action, idle, automatically disconnected)

2, then find "network security: forced logout after the login time is exceeded. The default is: disabled, must be changed to: enabled

The following describes some parameters of mstsc:

Mstsc (Microsoft terminal services client)

mstsc and remote client The connection is made by Microsoft's Remote Desktop Protocol (RDP), and the Windows XP rdp has a concurrency limit. For each user, The rdp file is stored as a hidden file in My Documents.

Create a connection to a terminal server or other remote computer, edit an existing Remote Desktop Connection (.rdp) profile, and connect your Windows XP (connection created using Client Connection Manager) Migrate to a new .rdp file.

mstsc Syntax

mstsc.exe {ConnectionFile /v:server} [/console] [/f] [/w:width /h:height]

mstsc. Exe /edit "ConnectionFile"

mstsc.exe /migrate

mstsc Parameters

ConnectionFile is specified for connection. The name of the rdp file

/v:server[;port] specifies the remote computer to connect to

/admin will connect to the session to manage the server

/f in full screen Start Remote Desktop connection in mode

/w:width Specify the width of the remote desktop window

/h:height Specify the height of the remote desktop window

/public in public Running Remote Desktop in Mode

/span is the height and width of the remote computer that matches the local virtual desktop and expands to multiple displays if necessary. To extend to multiple displays, all displays must have the same height and be aligned vertically

/console Connect to a console session specifying Windows 2000 Server

/edit Open the specified .rdp file Editing

/migrate Migrating legacy connection files created using the Client Connection Manager to a new .rdp connection file