![]() If the goal is to allow users to remote into the session host (part of RDS deployment, the server where you deploy and publish user software) then the remote connection was designed to be like this:Įxtuser > 443 > gateway > connection broker > session host. Similar connections happen when external users remote into their corporate computers from outside via the gateway. The connection will be as follows: extuser > 443 > Gateway portion > 3389 > Session Host (same box). Not that it maters in your single Session Host deployment, but using your approach will skip the Connection Broker part. If you want users to RDP into the RDS server only then technically you don't even need to publish the Remote Desktop Connection pointing to /v. Marking as it a Best Answer - hope that the contributors agree. If the above suggestion worked you gotta leave the v/ parameter pointing to the internal FQDN or, if you don't want to expose the internal FQDN make sure your internal DNS returns local ip of the gateway when is queried inside the network. The RD Gateway checks DNS and if the public IP is returned, then it tries to connect to itself over the WAN interface. When you are launching the published app you are connecting to the gateway over 443 and asking it to connect you to. Change it to internal FQDN of your all-in-one RDS box and post results. ![]() ![]() ![]() I assume your problem is the /v parameter looking at the external address.
0 Comments
Leave a Reply. |