I currently have a terminal server environment that consists of 1 domain controller and 1 terminal server.
All works well.
Now I have added a second terminal server - identical to the first, and a separate server to act as session broker.
I set everything up as per this guide:
MS session broker setup guide
However, once I put both of the servers into the farm, the main one always takes me on to the main one, and the second one refuses the connection.
I think there may be a complicating factor because the servers have local IPs assigned to their NICs, but we access them via public IP which is then NATed by a pfsense firewall - so I am wondering if when I log in to one of the servers, it is querying the session broker, determining that the other server should handle the logon, then redirecting to the local IP, which the "client" cannot access because they are connecting over the WAN..?
Its the first time I have set this up as well, which doesnt help.
Just wondering if anyone has any ideas?