Source address persistence.

Thanks wesleyjack , basically this VIP is for RDP connection only.We have used source persistence instead mrd persistence, thinking that impact would be that same. For this solution persistence will be required to ensure that once connected a user’s traffic always returns to the same TS server otherwise their session will be lost as there’s no TS Session Broker configured.

The issue is because the clients are NAT’d through the firewall to only five or so source addresses which are then identified by IP address:port number when the Load Balancer distributes them as soon as one hits a real server the persistence kicks in and every other client NAT’d to that IP address regardless of port number bypasses LB’ing to follow to the same real server. So either we use source or MRD persistence we will get the same result.

Any other approach to overcome this situation ?