I've been standing up a RemoteApp concept that somehow I was asked to host
in my home lab (long story). However, even though it works fine internally,
I am having some issues launching applications externally.

I've set up a server with the Remote Desktop Services Session Host,
Connection Broker, Gateway and Web Access roles. I have published a single
app through this (Notepad). I have set up dynamic DNS and am port
forwarding 443 inbound on the router onto the IP address of the RemoteApp
server. When I connect to https://dynamicdnsname/RDWeb externally, I can
log in and see my applications. However, when I try to launch one, I simply
get the usual RDP error screen

[image: Inline images 1]

I have changed the published name using the SetRDPublishedName cmdlet (
https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80)
so that the RDP connection points to my external dynamic DNS name

[image: Inline images 2]

I have also messed about with various IIS settings as per this post -
http://www.concurrency.com/infrastructure/remote-desktop-services/remote-desktop-cant-find-the-computer-through-rdweb-and-gateway/
- but this also doesn't seem to help.

It's a long time since I delved into RDS and RemoteApp, so have I
configured something incorrectly? Any help would be gratefully received
right now :-)


TIA,




JRR


-- 
*James Rankin*
---------------------
RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization
Practice Analyst - Desktop Virtualization
http://appsensebigot.blogspot.co.uk

Reply via email to