I'm in the process of setting up 3 Terminal servers for use by externally located individuals. I'm hoping to set them up with a Terminal Server Session Broker, but have a few questions before I finalize the plan.
The 3 Terminal Servers will be published externally via 3 ISA 2006 Standard servers. Each ISA server is on a different internet connection. For ease of use by end users, I'd like to only publish 1 TS per ISA server (since I'd have to set the second and 3rd to use non-standard ports to publish them).
The round robin-DNS would obviously be different internally than externally.
So, what I need to know, is when the Broker returns the Terminal Server to connect to back to the client, what will it return? With IP address redirection turned on, I kind of assume that the Session Broker will return the server's internal IP, since neither it, nor the terminal server itself, are aware that it's also associated with an external IP. I'm also assuming that this will prevent the client on the outside from being able to connect.
If I leave IP address redirection turned off, and stick with token redirection, will this work any better, or are the token's still based on IP?
Short of round-robin DNS, is there any way to effectively load-balance, or at least provide Session re-connection to clients outside the WAN?