Quantcast
Channel: Forum Remote Desktop Services (Terminal Services)
Viewing all articles
Browse latest Browse all 27650

Can't connect to internal machines via RDWEB

$
0
0

Thanks in advance for any help.

You cannot vote on your own postI currently have Windows 2012 R2 Remote Desktop services configured with RDWEB. From the Internet, the user can open https://mypublicdomain.com/rdweb, login, and click the icon for my RDS Session host farm to initiate a Remote Desktop services session to one of my hosts. This works great, the connection opens to my RD Connection Broker and a session on an RD host automatically opens (SSO works fine, no extra credential prompt)

 

However, when I click the "Connect to a remote PC" link on RDWEB and then enter the name of an internal PC, I get:

1. A login prompt (unexpected since I get SSO when connecting to the TS farm as mentioned above

2. When I enter my credentials, I get an error that it can't connect to the machine.

I've confirmed that

1. All users (domain) users have permission in the connection authorization policy

2. Resource access policy is set to allow connections to "all machines"

3. I've set the DefaultTSGateway property in IIS to the public FQDN for my RD farm.

4. The internal machines I'm trying to connect to are up and running and remote desktop connections directly to them from another internal machine work fine.

Here's what my environment looks like:

  1. Remote Desktop Services Gateway: RDSG1.myinternaldomain.local. This server also has remote desktop web access and I've published the public URL RDS.mypublicdomain.com with a trusted 3rd party SSL certificate (there's no trusted certificate for myinternaldomain.local)
  2. Remote Desktop Services Connection Broker: remote_desktop_connection_broker.myinternaldomain.local
  3. Remote Desktop Services Session hosts: RDSH1.myinternaldomain.local, RDSH2.myinternaldomain.local, RDSH3.myinternaldomain.local

Thanks!



Viewing all articles
Browse latest Browse all 27650

Trending Articles