R
Rob
Guest
We have a couple of Server 2008 machines running as terminal servers. We've
set up a TS Session Broker which works great as long as you are on the
internal network. The TS Session Broker is set up to use IP redirection to
reconnect to existing sessions...obviously using their internal IP addresses.
The problem is that the TS Session Broker will not work with ISA at all
since it is using internal IP addresses for redirection. When you set up the
server publishing rule you can set it up to use the internal IP of the server
running the session broker (we have it running on one of the Terminal
Servers). If you have a session on another maching then the session broker
attempts to revector the RDP client to that IP address but that IP address is
not accessible externally.
So your only option is to continue with NLB as your method to connect...BUT
session broker functionality is lost at this point and there is no session
directory to reconnect to an existing session since the new session broker
only uses IP redirection in the database.
First question, am I missing something that someone can clarify on how I can
use session broker via ISA server publishing rule?
If not, is there a way to cause Server 2008 to have the same functionality
as the session directory in 2003?
set up a TS Session Broker which works great as long as you are on the
internal network. The TS Session Broker is set up to use IP redirection to
reconnect to existing sessions...obviously using their internal IP addresses.
The problem is that the TS Session Broker will not work with ISA at all
since it is using internal IP addresses for redirection. When you set up the
server publishing rule you can set it up to use the internal IP of the server
running the session broker (we have it running on one of the Terminal
Servers). If you have a session on another maching then the session broker
attempts to revector the RDP client to that IP address but that IP address is
not accessible externally.
So your only option is to continue with NLB as your method to connect...BUT
session broker functionality is lost at this point and there is no session
directory to reconnect to an existing session since the new session broker
only uses IP redirection in the database.
First question, am I missing something that someone can clarify on how I can
use session broker via ISA server publishing rule?
If not, is there a way to cause Server 2008 to have the same functionality
as the session directory in 2003?