Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

External users cannot connect to RDS that are published on a Windows Server 2008 R2-based RD Gateway server through Forefront UAG


View products that this article applies to.

Symptoms

Remote Desktop Services (RDS) are published on a Remote Desktop Gateway (RD Gateway) server that is running Windows Server 2008 R2 through Forefront Unified Access Gateway (UAG) in a network environment. Sometimes, external users cannot connect to the published RDS, and they receive the following error message:


Your computer can't connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance.


Additionally, an event that resembles the following is logged on the RD Gateway server:

↑ Back to the top


Cause

This issue occurs because user connections are not closed correctly. Therefore, some Forefront Network (Edge) tunnels are leaked. When the number of concurrent connections to the RD Gateway server has reached the maximum number, all new connection requests are denied.

↑ Back to the top


Resolution

Hotfix information

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 website: 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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must have the Remote Desktop Gateway role service enabled.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix. To avoid restarting, stop the Remote Desktop Gateway role service.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.21xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Aaedge.dll6.1.7600.21100305,66430-Nov-201106:30x64
Tsproxy-edgeadapter-ppdlic.xrm-msNot Applicable3,01830-Nov-201106:57Not Applicable
Aaedge.dll6.1.7601.21869308,22430-Nov-201106:15x64
Tsproxy-edgeadapter-ppdlic.xrm-msNot Applicable3,01830-Nov-201106:39Not Applicable

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, 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

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_04844210638e2b7c6abc5008c88fcfe6_31bf3856ad364e35_6.1.7600.21100_none_56abd1ab16ac0574.manifest
File versionNot Applicable
File size711
Date (UTC)30-Nov-2011
Time (UTC)11:33
File nameAmd64_f144c73204e76604bc5f8c6cd9825bd4_31bf3856ad364e35_6.1.7601.21869_none_dc69a82e865c566e.manifest
File versionNot Applicable
File size711
Date (UTC)30-Nov-2011
Time (UTC)11:33
File nameAmd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.1.7600.21100_none_9ada634fff47b9f4.manifest
File versionNot Applicable
File size99,560
Date (UTC)30-Nov-2011
Time (UTC)11:33
File nameAmd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.1.7601.21869_none_9c890b45fc967e53.manifest
File versionNot Applicable
File size99,560
Date (UTC)30-Nov-2011
Time (UTC)11:33

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2649422
Revision : 1
Created on : 1/7/2017
Published on : 2/9/2012
Exists online : False
Views : 136