Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all articles
Browse latest Browse all 27765

Windows 2012 RDS configuration issues - "your computer can't connect to the remote computer because the Remote Desktop Gateway is temporarily unavailable"

$
0
0

Here is the configuration;

RDS-1.domain.com  - 10.10.10.1 = Connection Broker
RDS-2.domain.com  - 10.10.10.2 = Gateway (3rd party SSl certificate installed)
RDS-3.domain.com  - 10.10.10.3 = Session/Virtualization Host
RDS-4.domain.com  - 10.10.10.4 = Web Access (3rd party SSl certificate installed)

I can connect using RDS-2.domain.com internally with no issues configuring the RDS Gateway settings on the RDP client OR when I login to the Web interface. IIS is configured on RDS-2.domain.com and RDS-4.domain.com for binding on 443 using the correct 3rd party SSL certificate and has the FQDN set. The Router/Firewall has port 443 set to route incoming traffic to RDS-4 and 3389 to RDS-2. I can use a browser to connect to RDS-4.domain.com and I login with no issues, but when I click on a app I get;

 Your computer can't connect to the remote computer because the Remote Desktop Gateway
 is temporarily unavailable. Try reconnecting later or contact your network
 administrator for assistance.

When I configure the RDP client for RDS-2.domain.com in the RDS Gateway configuration I get;

 Your computer can't connect to the remote computer because the Remote Desktop Gateway
 is temporarily unavailable. Try reconnecting later or contact your network
 administrator for assistance.

I have configured RD CAP and RD RAP policies and have the SSL Certificate selected. SSL bridging is unchecked. Internal and External DNS is configured and working correctly. The RDS Gateway services are running, it sees and connects to the other servers as well as Active Directory. Do I need to open additional ports on my router/firewall? 



Viewing all articles
Browse latest Browse all 27765

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>