I have a Windows Server 2008 box with the following roles...
-TS Web Access
... and configuration:
-CAP: Includes domain users and no computer groups.
-RAP: Includes the AD Computer Group to which the terminal server is a member.
-I have a third-party signed SSL certificate installed on the gateway.
The server to which I'm trying to connect is a Windows Server 2003 instance running in Hyper-V as a member server running Terminal Services.
Testing I've done:
-From inside, I can connect to the TS Web Access site, click on the Remote Desktop tab, type in the terminal server's NETBIOS name and connect to it.
-From outside, I can connect to the TS Web Access site, click on the Remote Desktop tab, but get the "The computer cannot connect to the remote computer" MSTSC error message after filling in the terminal server's NETBIOS name and clicking Connect.
-From outside, I opened mstsc, specified the internal NETBIOS name of the terminal server on the General tab and the gateway FQDN in Advanced / Settings - THIS WORKS.
Here's where my questions begin:
1) This is my first TS Web Access deployment - should my terminal server already be populated in the Remote Desktop tab in TS Web Access? It seems like all of the computers specified in the RAP should be displayed, a la RWW. Otherwise users would have to memorize their computer/terminal server names.
2) If the MSTSC approach works, what am I missing in TS Web Access?