You have problems when you try to connect to the Remote Desktop Gateway (RD Gateway) that is hosted on a computer that is running Windows Server 2008 R2

Symptoms

Consider the following scenario:

• You install the Remote Desktop Gateway (RD Gateway) service on a computer that is running Windows Server 2008 R2.

• There are multiple certificate bindings on the port 443 of this computer.
  

In this scenario, the RD Gateway may not work correctly. The incorrect behavior depends on the certificate store name of the selected certificate binding. The following two values of the certificate store name for the binding causes different issues:

• Certificate store name is not NULL for the binding
  
  In this case, all connections go through except in the following scenarios:

  • Smart card authentication is configured on the RD Gateway-side.
    

  • Network Access Protection health checks are enforced on the client-side.

• Certificate store name is NULL for the binding
  
  In this case, all connections fail together, and you receive the following error message:

  Your computer can't connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance.

  At the same time, the following TerminalServices-Gateway event that has the ID 306 is added to the TerminalServices-Gateway log:
  Note To check whether the certificate store name is NULL, follow these steps:

  1. At the command prompt, type the following command, and then press ENTER:
     

     netsh http show sslcert

  2. Check the value for Certificate Store Name of the first binding that is listening on port 443. A value of (null) indicates that the certificate store name is NULL for that particular binding.

Cause

The issues occur because the RD Gateway service retrieves an incorrect certificate binding.

Resolution

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Status

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

More Information

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