Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
RemoteApps Through TS Web access and NAT Rules

Unanswered RemoteApps Through TS Web access and NAT Rules

  • Friday, August 17, 2012 9:05 PM
     
     
    Sign In to Vote
    0

    I have a network of three machines, one is the SQL and Active Directory server (10.1.1.2) One is the TS RemoteApp server (10.1.1.3) and the other the TS Gateway Server (10.1.1.4)  I have a public IP Address NATed to the TS Gateway Server for port 443 which then communicates with the TS RemoteApp Server to launch the TS Remote App.

    When I plug the public IP address into a browser I get the TS Web Access portal which is great.  When I try to launch the RemoteApp it gives me an error message:

    > Your computer can't connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect.  Type a valid remote desktop gateway address.  

    I notice that in the RemoteApp connection window that it is trying to launch 10.1.1.3 from the client machine.  

    How Do I set up TS Gateway and RemoteApp to NAT the public traffic to the internal network correctly?  


     

All Replies

  • Monday, August 20, 2012 9:33 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,


    If your RD gateway is unreachable,pls check the below article to see whether your RDgateway is published on the public network,your external public name can be resolved,and the necessary ports are open.
    RD Gateway deployment in a perimeter network & Firewall rules:http://blogs.msdn.com/b/rds/archive/2009/07/31/rd-gateway-deployment-in-a-perimeter-network-firewall-rules.aspx

    regards,

    Clarence

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Tuesday, August 21, 2012 5:32 PM
     
     
    Sign In to Vote
    0
    The RD Gateway server is not in a perimeter network though.  It is all in an internal network for simplication in the firewall.  The firewall NATs port 443 from the public IP Address to the internal IP of the RD Gateway Server.  The external public name is valid and resolves correctly to the external IP address of the network and the SSL Certificate on the RD Gateway is valid.