As it turns out, Terminal Server load balancing actually works, and my problem was something completely different: I had been using hostnames in the relevant policies that were resolved by local host entries on the SA. For some reason these policies didn't match when the TS connection was sent to another host in the farm (possibly TS session broker uses IP addresses as destinations when deflecting connections, couldn't find that out in detail). As soon as I directly used the IP addresses of the destination systems in my policies, the problem went away, and sessions were distributed to all terminal servers in the farm without further problems. Just a small display problem left, but one I can live with: The TS client will display the IP address of the inital host in it's address bar, not the one it's been connected to in the end.
... View more
Hi, I've seen this or similar questions in the archive, but unfortunately none of the posts had a useful answer... We're running into problems when our Windows people activate the TS Session Broker feature on a Server 2008 R2 terminal server farm: Each time a connection is redirected by the session broker to another server, the Juniper TS client is closed with a "server denied the connection" message. In our case, the session broker role is activated on one of the actual terminal servers. Our SSL-VPN box is a SA4500 running 7.1R5. Does anyone have a setup where this works?
... View more