Event ID 306 — RD Gateway Server Connections

Published: January 8, 2010

Applies To: Windows Server 2008 R2

red

For remote clients to successfully connect to internal network resources (computers) through a Remote Desktop Gateway (RD Gateway) server, clients must meet the conditions specified in at least one Remote Desktop connection authorization policy (RD CAP) and Remote Desktop resource authorization policy (RD RAP). RD CAPs specify who can connect to an RD Gateway server and the authentication method that must be used. RD RAPs specify the computers that clients can connect to through an RD Gateway server.

Note: A limit can be set on the RD Gateway server to restrict the maximum number of simultaneous client connections.

Event Details

Product: Windows Operating System
ID: 306
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_TUNNEL_CREATION_FAILED
Message: The user "%1", on client computer "%2", was not authorized to connect to the RD Gateway server because a tunnel could not be created. The following authentication method was attempted: "%3". The following error occurred: "%5".

Resolve

Configure the RD Gateway server to use the certificate for SSL

To resolve this issue, do the following:

  • If a certificate is installed that meets RD Gateway certificate requirements, configure the RD Gateway server to use the certificate for SSL. For information about certificate requirements, see the section "Certificate requirements" later in this topic.
  • If you do not have a certificate installed that meets RD Gateway requirements, obtain a certificate, install the certificate, and then configure the RD Gateway server to use the certificate for SSL. For information about how to obtain a certificate for RD Gateway, see "Obtain a certificate for the Remote Desktop Gateway server" in the Remote Desktop Gateway Manager Help in the Windows Server 2008 R2 Technical Library (http://go.microsoft.com/fwlink/?LinkId=178454).

Configure the RD Gateway server to use the certificate for SSL

You must use Remote Desktop Gateway Manager to configure the RD Gateway server to use the certificate for SSL. If you do this by using any other method, RD Gateway will not function correctly.

This procedure is not required if you created a self-signed certificate for RD Gateway. To confirm whether a self-signed certificate is installed on the RD Gateway server, open Remote Desktop Gateway Manager and then view the SSL Certificate tab, as described in the following procedure. On the SSL Certificate tab, the name of the local RD Gateway server will appear in the Issued by field. 

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To configure the RD Gateway server to use the certificate for SSL:

  1. Open Remote Desktop Gateway Manager. To open RD Gateway Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Gateway Manager.
  2. In the Remote Desktop Gateway Manager console tree, right-click the local RD Gateway server, and then click Properties.
  3. On the SSL Certificate tab, click Select an existing certificate for SSL encryption (recommended), and then click Browse Certificates.
  4. In the Install Certificates dialog box, click the certificate that you want to use, click View certificate, and then review the certificate properties to ensure that it meets RD Gateway requirements. For information about certificate requirements, see "Certificate requirements" later in this topic.
  5. If the certificate meets the requirements for RD Gateway, click Install. If the certificate does not meet the requirements for RD Gateway, select another certificate that does (if another certificate is available), or do the following:
    1. Obtain another certificate that meets RD Gateway certificate requirements. For information, see "Obtain a certificate for the Remote Desktop Gateway server" in the Remote Desktop Gateway Manager Help in the Windows Server 2008 R2 Technical Library (http://go.microsoft.com/fwlink/?LinkId=178454).
    2. Install the certificate on the RD Gateway server. For information, see "Install the certificate on the RD Gateway server" later in this topic.
    3. Configure the RD Gateway server to use the certificate for SSL. For information, see "Configure the RD Gateway server to use the certificate for SSL" later in this topic.
  6. Click OK to close the Properties dialog box for the RD Gateway server.
  7. If this is the first time that you have configured the RD Gateway server to use an SSL certificate, after the procedure is completed, you can confirm that the procedure was successful by viewing the RD Gateway Server Status area in Remote Desktop Gateway Manager. Under Configuration Status and Configuration Tasks, the warning stating that a server certificate is not yet installed or selected and the View or modify certificate properties hyperlink are no longer displayed.

Use the following procedure only if you do not have a certificate installed that meets RD Gateway requirements, and you have to obtain an alternate certificate for the RD Gateway server. In this case, after you obtain the certificate, you must install it on the RD Gateway server. Then, follow the steps in "Configure the RD Gateway server to use the certificate for SSL" to complete the certificate configuration.

Install the certificate on the RD Gateway server

To install the certificate on the RD Gateway server:

  1. On the Remote Desktop Gateway server, open the Certificates snap-in console. If you have not already added the Certificates snap-in console, you can do so by doing the following:
    1. Click Start, click Run, type mmc, and then click OK.
    2. On the File menu, click Add/Remove Snap-in.
    3. In the Add or Remove Snap-ins dialog box, in the Available snap-ins list, click Certificates, and then click Add.
    4. In the Certificates snap-in dialog box, click Computer account, and then click Next.
    5. In the Select Computer dialog box, click Local computer: (the computer this console is running on), and then click Finish.
    6. In the Add or Remove Snap-ins dialog box, click OK.
  2. In the Certificates snap-in console, in the console tree, expand Certificates (Local Computer), and then click Personal.
  3. Right-click the Personal folder, point to All Tasks, and then click Import.
  4. On the Welcome to the Certificate Import Wizard page, click Next.
  5. On the File to Import page, in the File name box, specify the name of the certificate that you want to import, and then click Next.
  6. If the Password page appears, if you specified a password for the private key associated with the certificate earlier, type the password, and then click Next.
  7. On the Certificate Store page, accept the default option, and then click Next.
  8. On the Completing the Certificate Import Wizard page, confirm that the correct certificate has been selected.
  9. Click Finish.
  10. After the certificate import has successfully completed, a message appears confirming that the import was successful. Click OK.
  11. With Certificates selected in the console tree, in the details pane, confirm that the correct certificate appears in the list of certificates on the RD Gateway server. The certificate must be under the Personal store of the local computer.

Certificate requirements

Certificates for RD Gateway must meet these requirements:

  • The name in the Subject line of the server certificate (certificate name, or CN) must match the DNS name that the client uses to connect to the RD Gateway server, unless you are using wildcard certificates or the SAN attributes of certificates. Multiple CNs are not supported. If your organization issues certificates from an enterprise certification authority (CA), a certificate template must be configured so that the appropriate name is supplied in the certificate request. If your organization issues certificates from a stand-alone CA, you do not need to do this.
  • The certificate is a computer certificate.
  • The intended purpose of the certificate is server authentication. The Extended Key Usage (EKU) is Server Authentication (1.3.6.1.5.5.7.3.1).
  • The certificate has a corresponding private key.
  • The certificate has not expired. We recommend that the certificate be valid one year from the date of installation.
  • A certificate object identifier (also known as OID) of 2.5.29.15 is not required. However, if the certificate that you plan to use contains an OID of 2.5.29.15, you can only use the certificate if at least one of the following key usage values is also set: CERT_KEY_ENCIPHERMENT_KEY_USAGE, CERT_KEY_AGREEMENT_KEY_USAGE, and CERT_DATA_ENCIPHERMENT_KEY_USAGE.
  • The certificate must be trusted on clients. That is, the public certificate of the CA that signed the RD Gateway server certificate must be located in the client's Trusted Root Certification Authorities store on the client computer.

Verify

To verify that RD Gateway server connectivity is working, examine Event Viewer logs and search for the following event messages.

To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.

To verify that RD Gateway server connectivity is working:

  1. On the RD Gateway server, click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-Gateway, and then search for the following events:
    • Event ID 101, Source TerminalServices-Gateway: This event indicates that the Remote Desktop Gateway service is running.
    • Event ID 200, Source TerminalServices-Gateway: This event indicates that the client is connected to the RD Gateway server.
    • Event ID 302, Source TerminalServices-Gateway: This event indicates that the client is connected to an internal network resource through the RD Gateway server.

 

Related Management Information

RD Gateway Server Connections

Remote Desktop Services

Community Additions

ADD
Show: