We help IT Professionals succeed at work.

External Connection Issue using TS Web Access

I am attempting to impliment a Terminal Server for external users and am having an issue with external access.  I am able to get to the TS Web and log into the site.  Remote Desktop Tab has been removed from Web Access so I can see the RemoteApp Programs and Configuration Tabs.  When launching an associated software I first get a warning that the publisher of the remote app cannot be identified after selecting "Connect" I get an error stating "The remote computer could not be found.  Please contact your Helpdesk about this error."  As mentioned this is ONLY happening externally and happens while connected via VPN as well.  I can take the same non-domained laptop into the office and connect without issue.

I would seem to me that this is some type of firewall issue or permissions issue while connecting outside of the office.  But obviously I am asking the question so may be completely clueless as well.. lol...  I have done the following.

1) verified https and rdp ports open to the TS on the firewall and all NAT looks correct.  I can rdp to the external ip and connect to the server in question.
2) worked through all settings as per Microsoft publication and rechecked - again all is as published.
3) read articles on EE as well on the net without much luck and tried suggested fixes with TS RemoteApp Manager and TS Gateway

The server on the domain is server.domain.net and externally resolving from https://tsserver.externaldomain.com/ts so I am also wondering if there is an issue there as well.

I am still only using a self signed cert as I am in the testing stage right now.  
Watch Question


problem is with server name, TS Web Access create page with original (internal), which is invisible from internet.
Try to clean dns cache on external computer - ipconfig /flushdns
Then try to connect
Check with ipconfig /displaydns which hostname wasn't able to find.
Why you don't implement TS gateway?
scottolesonCEO / President


The response on the external pc shows that the "server" (terminal server in the office) does not exist when displaying dns records.    So if I follow I should be picking up the dns records; but for which the internal server showing my 10.0.x.x or from my isp showing the external address??

Off Subject - As for the other question I have also installed the TS Gateway on the same 2k8 server.  For me the Web Access is needed as I have a CFO who is very visual.  Typically on a Verizon wireless card.  I am always getting calls as to why Outlook Anywhere is not working.  Duh he isn't connected to the internet.  Thus Web Access is simple since he can see that the web is not connected.  Long run will save me receiving calls in the middle of the night.  Not that I answer them now..  lol.

trouble is that external  address doesn't exist. When you created external name tsserver.externaldomain.com and you publish web under this name to internet, but TS Web Access has inside his web pages prepared connection to it's internal name, terminal server itself doesn't know about your external dns alias name.
So in that case you have these options: create same external dns record as internal servername or prepare desktop rdp link over ts gateway and teach your cfo to use it.
Technical Manager
Top Expert 2010
Qlemo"Batchelor", Developer and EE Topic Advisor
Top Expert 2015

This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
nappy_dThere are a 1000 ways to skin the technology cat.

For future reference, a TSGateway is not necessary.

The reason you are getting this error is because your server does not have a public FQDN.

You are most likely trying to access your remoteApp server from the internet via the NetBIOS name.

You have two options to get around this:

1. step1

FREE add an entry like this to your hosts file <yourServername     yourServerIPaddress> NOTE: THIS OPTION REQUIRES EVERY CONNECTING CLIENT COMPUTER TO HAVE THE HOSTS FILE EDITED

2. step2

ANNUAL FEE register your server to have a public name and IP such as remoteApp.myDomain.com