Event ID 627 — TS Gateway Server Configuration

Updated: January 5, 2012

Applies To: Windows Server 2008

red

For remote clients to successfully connect to internal network resources (computers) through a Terminal Services Gateway (TS Gateway) server, the TS Gateway server must be configured correctly. The TS Gateway server must be configured to use an appropriate Secure Sockets Layer (SSL)-compatible X.509 certificate, and authorization policy settings must be configured correctly. Terminal Services connection authorization policies (TS CAPs) specify who can connect to the TS Gateway server. Terminal Services resource authorization policies (TS RAPs) specify the internal network resources that clients can connect to through a TS Gateway server.

Event Details

Product: Windows Operating System
ID: 627
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.0
Symbolic Name: AAG_EVENT_LB_TSG_EXCEPTION_ENABLE_FAILED
Message: The Windows Firewall exception to allow network traffic through TCP port 3388 (so that Terminal Services client connections can be directed to the appropriate TS Gateway servers when load balancing is used) could not be configured.

Resolve

Manually enable the Terminal Services Gateway Server Farm exception

To resolve this issue, manually enable the Terminal Services Gateway Server Farm exception in Windows Firewall. You can configure this exception by using Windows Firewall in Control Panel or by using Group Policy.

Note:  The Terminal Services Gateway Server Farm exception in Windows Firewall should be enabled for all TS Gateway servers that are members of a TS Gateway server farm. For optimal security, for TS Gateway servers that are not members of a TS Gateway server farm, consider disabling this exception.

Enable the Terminal Services Gateway Server Farm exception by using Windows Firewall in Control Panel

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

To enable the Terminal Services Gateway Server Farm exception by using Windows Firewall in Control Panel:

  1. Open Windows Firewall. To open Windows Firewall, click Start, click Control Panel, and double-click Windows Firewall.
  2. In Windows Firewall, click Change Settings.
  3. On the Exceptions tab, enable the Terminal Services Gateway Server Farm exception by selecting the Terminal Services Gateway Server Farm check box.  If this check box is dimmed, Group Policy has been applied to control this exception. To modify Group Policy to enable this exception, see "Enable the Terminal Services Gateway Server Farm exception by using Group Policy" later in this topic.
  4. Click OK.
  5. Close Windows Firewall.

Enable the Terminal Services Gateway Server Farm exception by using Group Policy

To change Group Policy settings for a domain or an organizational unit (OU), you must be logged on as a member of the Domain Admins, Enterprise Admins, or the Group Policy Creator Owners group, or have been delegated the appropriate control over Group Policy.

To enable the Terminal Services Gateway Server Farm exception by using Group Policy:

  1. On a computer running the Group Policy Management Console, start the GPMC. To do so, click Start, point to Administrative Tools, and then click Group Policy Management.
  2. In the left pane, locate the OU that you want to edit.
  3. To modify an existing Group Policy object (GPO) for the OU, expand the OU, and then click the GPO.
  4. In the right pane, click the Settings tab.
  5. In the left pane, under Computer Configuration, expand Windows Settings, expand Security Settings, expand Windows Firewall with Advanced Security, expand Windows Firewall with Advanced Security, and then click Inbound Rules.
  6. If the rules associated with the Terminal Services Gateway Server Farm exception appear in the list of rules but are not enabled, proceed to step 7. If these rules do not appear in the list of rules, do the following to create and enable them:
    1. Right-click Inbound Rules, and then click New Rule.
    2. In the New Inbound Rule Wizard, on the Rule Type page, click Predefined, click Terminal Services Gateway Server Farm, and then click Next.
    3. On the Predefined Rules page, verify that three inbound rules appear (one for RPC-EPMAP, one for TCP-In, and one for RPC HTTP Load Balancing Service), and then click Next.
    4. On the Action page, select Allow the connection or Allow the connection if it is secure (and specify any additional options if needed) as appropriate for your environment, and then click Finish.
  7. To enable the rules associated with the Terminal Services Gateway Server Farm exception (if they appear in the list of rules and are disabled), right-click each of the following rules (TCP-In, RPC-EPMAP, and RPC HTTP Load Balancing Service), and then click Enable Rule.
  8. Close the Group Policy Management Console.
  9. Ensure that the update to Group Policy is applied by running the gpupdate /force command. To run the gpupdate /force command, click Start, click Run, type cmd, and then press ENTER. At the command prompt, type gpupdate /force and then press ENTER.

For more information about configuring Group Policy settings by using GPMC, see the GPMC Help  in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101634).

Verify

To verify that the TS Gateway server is configured correctly, examine Event Viewer logs and search for the following event messages. These event messages indicate that the Terminal Services Gateway service is running, and that clients are successfully connecting to internal network resources through the TS Gateway server.

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 the TS Gateway server is configured correctly:

  1. On the TS 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 Terminal Services Gateway service is running.
    • Event ID 200, Source TerminalServices-Gateway: This event indicates that the client connected to the TS Gateway server.
    • Event ID 302, Source TerminalServices-Gateway: This event indicates that the client connected to an internal network resource through the TS Gateway server.

Related Management Information

TS Gateway Server Configuration

Terminal Services

Community Additions

ADD
Show: