?
Solved

TS Web Access name resolution issues from outside

Posted on 2008-10-05
1
Medium Priority
?
1,038 Views
Last Modified: 2013-11-21
I have a Windows Server 2008 box with the following roles...
-TS Licensing
-TS Gateway
-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?

Thank you,
Nathan
0
Comment
Question by:nathanwc
1 Comment
 
LVL 1

Accepted Solution

by:
nathanwc earned 0 total points
ID: 22655680
Since I got no response here for 24 hours even with 500 points up for grabs, I had to call Microsoft PSS and free myself of $259. I did, however, get help with this article to which the MS tech pointed me:

http://technet.microsoft.com/en-us/library/cc731465.aspx

In particular, my "DefaultTSGateway" in IIS setting had no value. I had to assign it the external FQDN (that to which you assigned your SSL cert.)
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question