Event ID 301 — 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: 301
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_EVENT_RAP_FAILED
Message: The user "%1", on client computer "%2", did not meet resource authorization policy requirements and was therefore not authorized to resource "%4". The following error occurred: "%5".

Resolve

Ensure that the client meets the requirements of the RD RAP

To resolve this issue, ensure that the clients meet the requirements of at least one Remote Desktop resource authorization policy (RD RAP). To determine whether a client meets the requirements of at least one RD RAP, check the RD RAP settings on the RD Gateway server.

Note:  In addition to meeting the requirements of the RD RAP, users on clients must have the right to log on locally to the computer to which they are trying to connect.

Important:  If users are connecting to members of an RD Session Host server farm, you must configure an RD RAP that explicitly specifies the name of the RD Session Host server farm. If the name of the RD Session Host server farm is not explicitly specified, users will not be able to connect to members of the farm. For optimal security and ease of administration, to specify the RD Session Host servers that are members of the farm, create a second RD RAP. For more information, see "Create a new RD RAP that specifies the name of an RD Session Host server farm" later in this topic.

Check RD RAP settings on the RD Gateway server

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

Note:  When you associate an RD Gateway-managed computer group with an RD RAP, you can support both fully qualified domain names (FQDNs) and NetBIOS names by adding both names to the RD Gateway-managed computer group separately. When you associate an Active Directory security group with an RD RAP, both FQDNs and NetBIOS names are supported automatically if the internal network computer that the client is connecting to belongs to the same domain as the RD Gateway server. If the internal network computer belongs to a different domain than the RD Gateway server, users must specify the FQDN of the internal network computer.

To check RD RAP settings on the RD Gateway server:

  1. Open Remote Desktop Gateway Manager. To open Remote Desktop 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, select the node that represents the local RD Gateway server, which is named for the computer on which the RD Gateway server is running.
  3. In the console tree, expand Policies, and then click Resource Authorization Policies.
  4. In the results pane, in the list of RD RAPs, right-click the RD RAP that you want to check, and then click Properties.
  5. On the User Groups tab, note the name of the user group, so that you can ensure that the specified user group exists in Active Directory Domain Services or Local Users and Computers. Then, check whether the user account for the client is a member of this group. For instructions for Active Directory security groups, see "Confirm that the Active Directory security group specified in the RD RAP exists, and check account membership for the client in this group." For instructions for local security groups, see "Confirm that the local security group specified in the RD RAP exists, and check account membership for the client in this group" later in this topic.
  6. On the Computer Group tab, if Allow users to connect to any network resource is not selected, do one of the following:
    • If Select an existing Active Directory security group is selected, note the name of the security group, so that you can ensure that the specified group exists in Active Directory Domain Services or Local Users and Computers. Then, check whether the computer account for the computer that the client is trying to connect to is a member of this group.
    • If Select existing RD Gateway-managed computer group or create a new one is selected, ensure that the name of the RD Gateway-managed computer group is correct, and that the computers in this group exist and can be contacted on the network.
  7. Click OK to close the Properties dialog box for the RD RAP.
  8. If the client settings and RD RAP settings are not compatible, do one of the following:
    • Modify the client configuration.
    • Modify the settings of the existing RD RAP.
    • Create a new RD RAP. For information about how to create an RD RAP, see "Create an RD RAP" in the Remote Desktop Gateway Manager Help in the Windows Server 2008 R2 Technical Library (http://go.microsoft.com/fwlink/?LinkId=178450).

After you check RD RAP settings, ensure that the local or Active Directory security group specified in the RD RAP exists, and that the user account for the client is a member of the appropriate security group. Also, ensure that the computer group specified in the RD RAP exists.

Performing these procedures does not require membership in the local Administrators group. Therefore, as a security best practice, consider performing these tasks as a user without administrative credentials.

Confirm that the Active Directory security group specified in the RD RAP exists, and check account membership for the client in this group

To confirm that the Active Directory security group specified in the RD RAP exists:

  1. On a computer running Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then press ENTER.
  2. In the console tree, expand Active Directory Users and Computers/DomainNode/, where the DomainNode is the domain to which the security group belongs.
  3. Right-click the domain, and then click Find. In the Find Users, Contacts, and Groups dialog box, type the name of the security group that is specified in the RD RAP, and then click Find Now.
  4. If the group exists, it will appear in the search results.
  5. Close the Find Users, Contacts, and Groups dialog box.

To check account membership for the client in this security group:

  1. On a computer running Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then press ENTER.
  2. In the console tree, expand Active Directory Users and Computers/DomainNode/Users, where the DomainNode is the domain to which the user belongs.
  3. In the details pane, right-click the user name, and then click Properties.
  4. On the Member Of tab, confirm that one of the groups listed matches one of the groups that is specified in the RD RAP.
  5. Click OK.
  6. Expand Active Directory Users and Computers/DomainNode/Computers, where the DomainNode is the domain to which the computer that the client is trying to connect to belongs.
  7. In the details pane, right-click the computer name, and then click Properties.
  8. On the Member Of tab, confirm that one of the groups listed matches one of the groups that is specified in the RD RAP.

Confirm that the local security group specified in the RD RAP exists, and check account membership for the client and the target computer in this group

To confirm that the local security group specified in the RD RAP exists, and to check account membership for the client and the target computer in this group:

  1. On the Remote Desktop Gateway server, open Computer Management. To open Computer Management, click Start, point to Administrative Tools, and then click Computer Management.
  2. In the console tree, expand Local Users and Groups, and then click Groups.
  3. In the results pane, locate the local security group that has been created to grant members access to internal network resources (computers) through the RD Gateway server. The group name or description should indicate whether the group has been created for this purpose.
  4. Right-click the group name, and then click Properties.
  5. On the General tab, confirm that the user account is a member of this group, and that this group is one of the groups that is specified in the RD RAP.
  6. Click OK to close the Properties dialog box for this security group.
  7. In the results pane, locate the local security group that contains the computers that clients can access through the RD Gateway server.
  8. Right-click the group name, and then click Properties.
  9. On the General tab, confirm that the computer account of the target computer (the computer that the client is trying to connect to) is a member of this group.

Create a new RD RAP that specifies the name of an RD Session Host server farm

Complete the steps in the following procedure if this error occurs when clients are connecting to members of an RD Session Host server farm.

Important:  If users are connecting to members of an RD Session Host server farm, you must configure an RD RAP that explicitly specifies the name of the RD Session Host server farm. If the name of the RD Session Host server farm is not explicitly specified, users will not be able to connect to members of the farm. For optimal security and ease of administration, to specify the RD Session Host servers that are members of the farm, create a second RD RAP.

When you create a second RD RAP to specify the RD Session Host servers that are members of the farm, complete the steps in the following procedure, but for step 9, do the following instead: On the Computer Group tab, select the Select an Active Directory security group option, and then specify the security group that contains the RD Session Host servers in the farm. Doing this optimizes security by ensuring that the members of the farm are trusted members of an Active Directory security group.

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

To create a new RD RAP that specifies the name of an RD Session Host server farm:

  1. Open Remote Desktop Gateway Manager. To open Remote Desktop Gateway Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Gateway Manager.
  2. In the console tree, click to select the node that represents your RD Gateway server, which is named for the computer on which the RD Gateway server is running.
  3. In the console tree, expand Policies, and then click Resource Authorization Policies.
  4. In the console tree, right-click the Resource Authorization Policies folder, click Create New Policy, and then click Custom.
  5. On the General tab, in the Policy name box, enter a name that is no longer than 64 characters.
  6. In the Description box, enter a description for the new RD RAP.
  7. On the User Groups tab, click Add to select the user groups to which you want this RD RAP to apply.
  8. In the Select Groups dialog box, specify the user group location and name, and then click OK. To specify more than one user group, do either of the following:
    • Type the name of each user group, separating the name of each group with a semi-colon.
    • Add additional groups from different domains by repeating step 7 for each group.
  9. On the Network Resource tab, do the following:
    1. Click Select an existing RD Gateway-managed computer group or create a new one, and then click Browse.
    2. In the Select a RD Gateway-managed computer group dialog box, click Create New Group.
    3. On the General tab, type a name and description for the new group.
    4. On the Network Resources tab, type the name of the RD Session Host server farm that you want to add, click Add, and then click OK to close the New RD Gateway-Managed Computer Group dialog box.
    5. In the Select a RD Gateway-managed computer group dialog box, click the name of the new computer group, and then click OK to close the dialog box.
  10. On the Allowed Ports tab, do one of the following to specify the port that Remote Desktop Services clients can use when connecting to computers through RD Gateway:
    • To specify different ports through which clients can connect, click Allow connections through these ports and then type the port number. If you are specifying more than one port, type the number for each port separated by a semi-colon.
    • To allow clients to connect through any port, click Allow connections through any port.
  11. Click OK to close the Properties dialog box for the RD RAP.
  12. The new RD RAP that you created appears in the Remote Desktop Gateway Manager results pane. When you click the name of the RD RAP, the policy details appear in the lower pane.

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: