The most efficient solution for WIN2003 servers exceeding the maximum allowable number of connections _win server

There are many ways to solve this, if you need to log on to the server immediately, the easiest way is:

Start-run-mstsc/console/v: server name or IP or domain name: Remote port:

such as: mstsc/console/v:222.222.215.222:3389

Why: 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" error that causes a failure to log on to the terminal server properly. 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, if you do not exit by logging off, Instead of simply shutting down the Remote Desktop window, the conversation is not released, but continues to remain on the server side, which takes up the total number of links, which appears when the number reaches the maximum allowable value.

Five steps to avoid landing error

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

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.

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-sessions

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 Limit number of connections to the right-select enabled-fill in the maximum number of connections allowed

Iv. changing the remote terminal mode

Recommended Use:

Start-Administration Tools-Terminal Services Configuration-server configuration-restricts each user to a single session

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

The default is: 15 minutes, to change 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

Here are some of the mstsc parameters:

MSTSC (Microsoft Terminal Services Client)

MSTSC is connected to remote clients by Microsoft's Remote Desktop Protocol (remotely Desktop Protocol, or RDP), while Windows XP RDP has 1 concurrent connection limits. 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) configuration file, and migrate Windows XP connections (connections created using Client Connection Manager) 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 Specifies the name of the. rdp file to use for the connection
/v:server[;p ORT] Specifies the remote computer to connect to
/admin will connect to the session to administer the server
/F to start the Remote Desktop Connection in full screen mode
/w:width Specifies the width of the Remote Desktop window
/h:height Specifies the height of the Remote Desktop window
/public running Remote Desktop in common mode
/span is the height and width of the remote computer that matches the local virtual desktop. Extend to multiple monitors if necessary. To extend to more than one monitor, all display must have the same height and vertically arrange the
/console Connect to the console session of the specified Windows Server
/edit Open the specified. rdp file for editing
/migrate will use the Legacy connection files created by Client Connection Manager migrate to a new. rdp connection File

If you feel more trouble, you can use the remote terminal to strengthen the version, forcing the login

Windows terminal Connector enhanced download