Solved

TS Web Access name resolution issues from outside

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

[Webinar] Disaster Recovery and Cloud Management

Learn from Unigma and CloudBerry industry veterans which providers are best for certain use cases and how to lower cloud costs, how to grow your Managed Services practice in IaaS clouds, and how to utilize public cloud for Disaster Recovery

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Trying to create a report out of AD 2008 2 29
How to get AD RMS to work with Office 2016 for Mac 6 163
sccm client without collection 1 41
vmdk greater than 2TB 2 31
I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

863 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

Need Help in Real-Time?

Connect with top rated Experts

26 Experts available now in Live!

Get 1:1 Help Now