[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 764
  • Last Modified:

RDS 2012 R2 Unable to connect to published desktop via RD Web Access

I've got a client that I'm trying to setup RDS.  I have everything working and can login via RDS Client on Windows 7 Pro remotely.  The issue is when I attempt to connect via the RD Web Access and click the published desktop I want to connect to I am seeing that the "gateway" and "remote computer" are listed as the same name "gateway.company.com".

The settings should be:

Remote Computer - rds1.company.com
Gateway - gateway.company.com

How can I get the correct remote computer name in the published desktop connection on RDweb?

One thing that I can not change is the fact that when I inherited the client their AD and external domain name are the same.
  • 5
1 Solution
Cliff GaliherCommented:
It sounds like the published remote desktop in the session collection is simply configured wrong. The rep file is automatically generated from those settings.
crystalinkAuthor Commented:
I deleted it and recreated the published desktop and the session host is set correctly.  I'm not seeing anywhere else to make a change in the session settings.
When you connect thrugh rd web access to RD Session host servers \ remote apps, the remote computer must be your RD connection broker and it will take care of providing you RD session host server
You RD Session host server will not come in picture directly

Have you installed RD gateway on same server as connection broker ?
If not Gateway server name and RD Connection broker name must be different
Ensure that your RD gateway server is publishhed on internet and tcp 443 is allowed from internet
Also RD gateway certificate must match to RD Gateway external FQDN
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

crystalinkAuthor Commented:
If I manually plug in the information into RDS client the system works perfect.  The issue is that the RDweb published session has the incorrect information in it and I can not find where that information can be changed in any of the settings.

Yes. I have the RD gateway on the same server as the connection broker.  The RD gateway is published and works fine with the stand-alone client, just not through the web access page.

I have a purchased 3rd party SSL cert.  It is correct.
crystalinkAuthor Commented:
Here is what the RDweb connection details are providing.
crystalinkAuthor Commented:
I got it to work.  There was a setting in the RD Gateway Manager RAP Policy that needed to be set to allow access to all network resources.
crystalinkAuthor Commented:
I figured this out from another website.

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now