Hi, I would like to provide high availability/scalability for my application. So, I am planning to use Network Load Balancing feature of Windows Server 2003. I have the following some basic questions on NLB, * All my application real servers are geographically distributed. All the servers can be in any network, but the routes between servers are properly configured. That means, each and every servers can be communicate with any other servers. Is it possible to setup NLB between those servers ? If so, please let me know the requirements for such setup. * Can I setup NLB with the following IP configurations, o Option 1 : + Real Server - 1 [ 192.168.118.124 ] + Real Server - 2 [ 192.168.118.178 ] + Cluster/Virtual IP Address [ 192.168.100.100 ] o Option 2: + Real Server - 1 [ 192.168.118.124 ] + Real Server - 2 [ 192.168.112.96 ] + Cluster/Virtual IP Address [ 192.168.100.100 ] * I tried to setup NLB with the following configuration, o Real Server - 1 [ 192.168.118.124 ] o Real Server - 2 [ 192.168.118.178 ] o Cluster/Virtual IP Address [ 192.168.118.33 ] o Port Rules : + Port Range : 6262 - 6262 + Protocols : TCP + Filtering mode : # Multiple host --> Affinity : Single My application server will provide service over https ( SSL over webserver). In the above, configuration the load balancing is working fine, ie, if I connect to the cluster IP from CLIENT-A m/c browser, it goes to RS1 and at the same time if I connect from CLIENT-B m/c browser it goes to RS2. It is perfectly working. But, now I shut down my application server which runs on RS1. So, my server is only running on RS2. Now, I tried to connect to the cluster IP from CLIENT-B m/c browser and I expected that the CLIENT-B m/c browser should connect to RS2 since RS1 is not running. But it is not happening. I says 'Connection refused' message on the browser. Am I missing anything ? What should I do for giving high availability for my application ? I greatly appreciate your help on the above questions/issue. Thanks, Ramesh