RDS 2012 R2 using 1 gateway, 2 session hosts and (right now) 1 connection broker. If i use RDC (on the local LAN) to remote to session host 1, somehow i end up on session host 2? Because i am using the private ip of session host 1, i am presented with a certificate error that tells me sessionhost1.domain.local. I click Yes and then i am presented with another certificate from sessionhost2.domain.local. I go ahead and click Yes to verify that i am landing on sessionhost2 and sure enough, computer name of the server is sessionhost2, not sessionhost1. I typed in the private ip of sessionhost1! What is redirecting the RDC to sessionhost2? This happens on both the local administrator and the domain users.

When i RDC to sessionhost2, that one does NOT redirect me to sessionhost1. These are "load balanced" in the collection

• Edited by forgiven 4 hours 37 minutes ago

Hi,

What you are seeing is normal.

When you need to connect to a specific RDSH server that is part of a load-balanced collection you need to use /admin, like this:

mstsc /admin

-TP