[THIN] Win2K3 WTS Load balancing over two networks

  • From: "Richard Manson" <rim@xxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 28 May 2004 01:00:02 +0200



Currently I have a Win2K3 TS server which offers services to computers from
two distinct networks: 

-         to computer from our Intranet, let's says this is network A

-          to computer from another corporate, this will be network B

The server is located on a A network (10.x.x.x) in order to be able to
access to our applications servers (databases and so forth).


This server has its address translated into the B network address space
(currently using a Cisco Catalyst).

Therefore, clients belonging to the B network can seamlessly connect to our


 In order to improve availability and as well increase the processing power,
I would like to add another server.
I had liked to balance the load among the two servers and therefore I
thought of using a "Session directory".

 My original scheme was the following:
- define a NLB 'cluster',
- put a session directory on another server "SDserver".
- translate the IP address for "SDserver" at the router level, as well as
the TS servers addresses.

 But from what I understand, the session directory will return to the client
the "A" network address for the elected TS server. It will not know about
replying the "B" address to clients belonging to the "B" network. 
 And given the "A" address, the client on the "B" network will hardly know
how to connect!

 Is there a way to work around this problem? 

Does exists other solution than a Session Directory and NLB Cluster for this


 Thanks for any input


This Week's Sponsor - Tarantella Secure Global Desktop
Tarantella Secure Global Desktop Terminal Server Edition
Free Terminal Service Edition software with 2 years maintenance.
Useful Thin Client Computing Links are available at:
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:

Other related posts:

  • » [THIN] Win2K3 WTS Load balancing over two networks