Solved

TS Web Access name resolution issues from outside

Posted on 2008-10-05
1
1,020 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

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

770 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