Hello, I''ve got 5 Windows 2003 Terminal Servers setup with Windows Network Load Balancing and part of a Session Directory. This means that the 5 TSs each have an individual IP but also share a common IP. The TS Farm is presented on the common IP so when you attempt to connect the the common IP one of the TSs picks up your request in a round robin fashion. Once your login creds are validated, the TS also check the Session Directory to see if your login currently has a session on another TS. If it does, then that TS redirects you to the TS you were on and your session picks up where you left off. This is a really cool feature and works perfectly within the local network. My problem is that the TSs are in a datacenter so the users will be connecting remotely. My first choice for this connection is to use OpenVPN and have each user access the terminal servers through the actual TS common IP via the VPN. My second choice is a DNAT with a public IP at the firewall. My problem is that neither of these work when redirected to an existing session. If the user doesn''t have a session then they can use the TS they originally connected to just fine. But if the Session Directory attempts to redirect - the RDP client just fails. Additional possible issues: The NICs are Broadcom GbE Teamed for failover. The network load balance cluster is set in Multicast mode. If I set them in Unicast mode I can''t ping in or out on the common or dedicated IPs. Any help, advice, pointers to how-to''s is greatly appreciated. Thanks -- -- W. Chris Shank ACE Technology Group www.myRemoteITdept.com ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer''s challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/