This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You configure the Maximum connections option in the Terminal Services Configuration window in a Windows Server 2008 system.
You make new connections until you reach the maximum number of connections.
You disconnect some active connections.
You try to create new Terminal Services sessions.
In this scenario, you cannot create the new Terminal Services sessions. You also receive the following error message:
The client could not establish a connection to the remote computer.
The most likely causes for this error are: 1) Remote connections might not be enabled at the remote computer. 2) The maximum number of connections was exceeded at the remote computer. 3) A network error occurred while establishing the connection. 4) The remote computer might not support the required FIPS security level. Please lower the client side required security level policy, or contact your network administrator for assistance.
Note You expect to be able to make new Terminal Services connections until the number of active Terminal Services sessions reaches the maximum limit.
This problem occurs because the disconnected Terminal Services sessions are calculated incorrectly when the system determines whether the maximum connection limit has been reached.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
To apply this hotfix, you must have Windows Server 2008 installed.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.
You do not have to make any changes to the registry to apply this hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008 note
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the Additional files for all supported x86-based versions of Windows Server 2008 section. MUM and MANIFEST files, and their associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files (file attributes not listed in this article) have a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
For all supported x64-based versions of Windows Server 2008
For all supported Itanium-based versions of Windows Server 2008
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To set the maximum number or connections for the Remote Desktop Protocol-Transmission Control Protocol (RDP-TCP) configuration, follow these steps:
Open Terminal Services Configuration. To do this, click Start, click Run, type tsconfig.msc, and then press ENTER.
In the console tree, click Connections, right-click RDP – Tcp in the right pane, and then click Properties.
Note The RDP – Tcp Properties dialog box opens.
Click the Network Adapter tab.
In the Network adapter field, click Maximum connections. Then, enter the limitation value.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Vista and for Windows Server 2008
Additional files for all supported x86-based versions of Windows Server 2008
Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Standard without Hyper-V, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard