Jump to content

Recommended Posts

Posted

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

Posted
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
  • Thanks 1
Posted

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.

Posted

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

  • Thanks 1
Posted
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.
Posted
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.

  • Thanks 1
Posted
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?

Posted

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

Posted
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.

Posted
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]

Posted
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.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...