We have a Windows 2012 R2 RDS environment that we have been using successfully for sometime for our ERP solution. We recently made an acquisition and discovered that their primary subnet was the same as the subnet we use for our server environment. We working to make changes, but in the mean time we have setup NAT rules on each end of a point to point connection facility normal traffic, and a trust between the domains. This is all working wonderfully, until we got to allow users on their side of the connectivity to our ERP solution through RDS.
Out Environment
1 RDS Connection Broker
1 RDS Licensing Server
1 RDS Web Access Server
6 RDS Session Hosts (Prod)
1 RDS Session Host (Test)
Some of the testing appears to show the RDS Connect Broker communicating with the Client, up until point that it attempts to redirect the client to the Session Host. We see the Client starting to broadcast a Who Is for the actual IP of the Session Host. Which of course is going to fail, both client and Connection Broker then time out trying to communicate.
My Question: Is the RDS Connection Broker redirecting bases off of the IP or FQDN of the Session, and if it is by IP, is there a way to have it use the FQDN.. other input and suggestions are also welcome.