Way back in August of '14 I posted about being perplexed over RD Gateway Server FQDN vs. Certificate Subject Name. Well, I did manage to get everything working BUT still to this day the external and internal hostnames do not match (a natural byproduct of using a different external and internal domains, so very common I'm sure). To illustrate, we have these two FQDN's for the server (private vs public):
- TS.private.com (the RD Gateway server and, for all intents and purposes here, the only TS/RDS server) **VERSUS**
- RDS.public.com (which our https://rds.ourdomain.com/rdwebsite directs to, 3rd party SSL cert and all are legit).
"TS.private.com" now has a DNS A record (inside our LAN only) to make the public name"rds.public.com" resolve to its private IP (192.168.x.x) as of today. I'd now like to simply update IIS bindings to use the PUBLIC...