Kyle Power
asked on
RDS 2016 - RemoteApp not working externally
A customer has a 2016 RDS deployment, currently one server is the Connection Broker, Session Host, Gateway, Licensing and Web Access. There are also 2 additional session hosts. RemoteApps are working internally, but externally when you click on an app, the users get prompted for credentials, but always get the error message below. When using RDP to connect externally to the RD Gateway, you can connect. So it just seems to be an issue with RemoteApp. Oddly enough, this was also happening to another server I was testing internally too, the only difference there was that it was not part of the domain.
Cliff Galiher
Usually means the collection was not created properly. People doing round Robin DNS or lunging settings. So the settings in the remote app file aren't correct.
ASKER
Cliff, would you please be a little more specific?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad you found a solution. To be clear though, that issue impacts *all* RDGateway traffic. Based on your description, you said you could RDP via the Gateway and *only* remoteapps were broken. Thus that isn't a solution most experts would have thought to suggest because it doesn't match the symptoms. I offer this as advice for future questions you may run into when asking on Experts Exchange.
ASKER
Thanks Cliff, what I said was true though, I WAS able to RDP in, but RemoteApp was not working. I was careful to be detailed in my observations of the issue.
ASKER
Solution above.