Solved

TS Web Access name resolution issues from outside

Posted on 2008-10-05
1
1,030 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

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

Suggested Solutions

If you migrate a Terminal Server licenses server inside the 2008 server family, you can takte advantage of the build-in migration tool. If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you …
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 configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
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 …

726 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