We recently setup a Windows 2016 RDS collection. This consists of the following servers:
- Server 1 (RDS Broker, RDS Licensing)
- Server 2 (RDSH)
- Server 3 (RDSH)
- Server 4 (RDS Web Access & RDS Gateway) (server 4 is located in our dmz)
We have an external dns record "apps.somedomain.co.uk" which points to server 4.
We have an internal dns record "rds.somedomain.local" which points to server 1.
We can successfully browse and log into https://apps.somedomain.co.uk\rdweb, however, when we attempt to connect to the RDSH farm, using the RDP shortcut within the RDWeb portal, it attempts to log us directly onto the gateway/web access server (server 4) rather
than query the broker and direct the session onto one of the RDSH servers!
Internally, if we RDP to rds.somedomain.local we are successfully redirected to one of the RDSH servers and we can see user session are being load balanced.
We have deleted and recreated the rds collection but we get the same issue. Below is a screen shot of what we see when using the RDP shortcut within the RDWeb portal. It appears both the 'remote computer' and the 'gateway' are pointing to the same dns record which resolves to the gateway/web access servers. How can we update the collection settings so the RDP shortcut has the correct dns address for both remote computer (ie: rds.somedomain.local) and gateway server (apps.somedomain.co.uk)?