Special Considerations for TS Gateway

Applies To: Windows Server 2008

The following are special considerations for TS Gateway in Windows Server 2008.

TS Gateway server considerations

Following are special considerations for the TS Gateway server.

Name resolution issues

When remote users attempt to access a computer on the internal corporate network through a TS Gateway server, they can specify either a NetBIOS name or a fully qualified domain name (FQDN) for the computer that they are attempting to connect to. When users specify the FQDN name of the target computer, and the associated Terminal Services resource authorization policy (TS RAP) that is configured on the TS Gateway server uses a NetBIOS name for the target computer, the client connection will succeed.

However, if the user attempts to connect to the target computer by using its NetBIOS name when the TS RAP configured on the TS Gateway server uses an FQDN name for the target computer, name resolution will fail and the user will not be able to connect to the target computer.

To avoid name resolution failure, and to support either NetBIOS names or FQDNs, include each possible computer name in the computer group that you create when you configure a TS RAP. For example, the computer names MySAPReportingServer and MySAPReportingServer.seattle.corp.microsoft.com would each need to be included in the computer group that you create, although both names represent the same computer.

Terminal Services client considerations

Following are special considerations for the Terminal Services client, when the client is used for connections through a TS Gateway server.

Automatic reconnection to a TS Gateway server might fail after the Terminal Services client comes out of hibernation

After you establish a remote connection through a TS Gateway server to another computer, if the Terminal Services client that initiated the connection hibernates and then comes out of hibernation, the client might not automatically reconnect to the remote computer through the TS Gateway server. To resolve this problem, open Task Manager, end the mstsc (Remote Desktop Connection) process, and then attempt the remote connection again. Closing mstsc will not resolve this problem.

TS Gateway server connection requests from a client running Windows XP with SP2 might fail if a smart card is used for authentication

If you are using a client running Windows® XP with SP2 to connect to a remote computer through a TS Gateway server, you will receive an error message stating that the remote computer is misconfigured if you do the following:

  1. Connect to a remote computer and leave your smart card in the smart card reader during the session.

  2. End the session, leaving the smart card in the smart card reader.

  3. Start another connection while leaving the smart card in the smart card reader.

To resolve this problem, remove the smart card, reinsert it, and then try to connect to the remote computer again.