load balance MSRDP traffic

Hi Phillip,

 

 

I don't think that will work, as the TCP won't contain the hostname. To test this, try capturing a tcpdump on your client using Wireshark while you connect using RDP to a remote host. You can try testing by IP address, hostname or using a fake hostname set in your hosts file for the remote host. I don't think you'll see the hostname or the hosts file entry in the TCP packets your client sends to the remote host. This is because RDP doesn't have a concept of host header like HTTP does. The client just resolves the hostname to an IP address and then attempts to establish the RDP connection with that IP address.

 

 

This means you'll need to have separate IP:port combinations for each RDP pool. If you don't want to require clients to specify the port when using mstsc, you'll need to have separate VIPs each defined on port 3389 for each pool.

 

 

Aaron