MS2011 Posted November 15, 2017 Posted November 15, 2017 Hi I'm running a test environment trying to deploy Microsoft's Remote Desktop Services to deploy a RemoteApp off Windows Server 2012R2. I have all services (RD Connection Broker, RD Gateway, RD Web Access, RD Session Host) on one server. Everything works fine on a domain-joined Windows 10 or 7 computer on our internal network. On an external computer on an external network, following happens: • I can view that I have a RemoteApp published. I click on it to download the .rdp file for the RemoteApp. • I run the .rdp file and am prompted for credentials to connect to servername.mydomain.com. I enter my domain credentials as I did to access the RDWeb page. • An error appears reading "Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance." • Ports opened TCP 443 , UDP 3389.. I have also tried disabled windows firewall on the RDS server. Thanks MS
jthompson Posted November 15, 2017 Posted November 15, 2017 Have you also tried supplying the username as domain\username?
MS2011 Posted November 15, 2017 Author Posted November 15, 2017 Hi Checked rap and cap rules, configured correctly. And also supplying the username as domain\username. Thanks
mukz Posted November 15, 2017 Posted November 15, 2017 What gateway does it say it is attempting to connect to? I assume it is the external FQDN? 1
Liam Posted November 15, 2017 Posted November 15, 2017 In the backend it will ask what resources you want to allow. As a test click any resource. Maybe you have just added a server group or something 1
MS2011 Posted November 16, 2017 Author Posted November 16, 2017 Your computer can’t connect to the remote computer because Rd gateway server is temporarily unavailable
jthompson Posted November 17, 2017 Posted November 17, 2017 It's a while since I did any of this, but I used this guide when I built ours - https://msfreaks.wordpress.com/2013/12/09/windows-2012-r2-remote-desktop-services-part-1/. Perhaps there's something in there which you might spot?
Decimas6 Posted November 17, 2017 Posted November 17, 2017 (edited) I just configured RDS for us here. I got this error when I had the RD Gateway server name entered wrongly and when certificates were not trusted. This is what I followed https://www.virtuallyboring.com/setup-rd-gateway-role-on-windows-server-2012-r2/ Edited November 17, 2017 by Decimas6 1
ITGURU Posted November 17, 2017 Posted November 17, 2017 Had this originally when I set it up a few years ago, but was down to the certificates on the server within the RDgateway. Also,you don't need port 3389 opened for the RemoteApps to work I only have port 443 open to the server.
Liam Posted November 20, 2017 Posted November 20, 2017 i seem to remember having to change the connection via a powershell cmdlet. I cant remember what it was now but i think i had configured the internal name 1
MS2011 Posted November 20, 2017 Author Posted November 20, 2017 Thanks for your response. Decimas6 - I’m going follow the guide you sent. Did you buy third party ssl certs?
cscc Posted November 20, 2017 Posted November 20, 2017 Had the same issue here before, off the top of my head the fix was adding the groups/users you wish to allow access to into the local Remote Desktop Users group on the RDS server.
Decimas6 Posted November 20, 2017 Posted November 20, 2017 Thanks for your response. Decimas6 - I’m going follow the guide you sent. Did you buy third party ssl certs? We already had this certificate for our external facing server so did not need to buy/set one up. 1
MS2011 Posted November 20, 2017 Author Posted November 20, 2017 We already had this certificate for our external facing server so did not need to buy/set one up. Do I need to get a wildcard cert or just for RD gateway?
MS2011 Posted November 21, 2017 Author Posted November 21, 2017 Hi For third party SSL Cert.. I am running all the RDS roles on one server. I am going to create the request on the RDS server, that has IIS and running the RD Web Access and create the request there. Once I get the cert, load it on the RD Web Access ( IIS ). And can deploy the same cert to the RD Gateway? Thanks MS
Decimas6 Posted November 27, 2017 Posted November 27, 2017 Hi For third party SSL Cert.. I am running all the RDS roles on one server. I am going to create the request on the RDS server, that has IIS and running the RD Web Access and create the request there. Once I get the cert, load it on the RD Web Access ( IIS ). And can deploy the same cert to the RD Gateway? Thanks MS Sorry for the late reply, is the RDS server going to be accessed from the web or internally only? I would set it up with your own certificates first as in the link I followed, check it all works then look into getting registered certs and what you need to do. We already had an exteral facing web server setup and I did not need to go through that part of the process.
dapaulio Posted November 27, 2017 Posted November 27, 2017 Had this originally when I set it up a few years ago, but was down to the certificates on the server within the RDgateway. Also,you don't need port 3389 opened for the RemoteApps to work I only have port 443 open to the server. I second this response [emoji106]
MS2011 Posted November 30, 2017 Author Posted November 30, 2017 Hi Anyone has implemented two factor authentication to RD web and remoteapp logon? Thanks MS
dapaulio Posted November 30, 2017 Posted November 30, 2017 Hi Anyone has implemented two factor authentication to RD web and remoteapp logon? Thanks MS Not here. I am trying to move staff away from rd and push staff towards o365. I recommend you open a new thread with your question.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now