Windows Server 2008 R2 NLB - multiple subnet issue
Hello All,
We have the following problem the with a MS NLB Cluster:
On site "Head-Office" we have configured a UniCast Microsoft NLB-cluster "RDS-Cluster"
(ipadress: 192.168.0.185) with machine "Cluster-A" (ipadress: 192.168.0.182) & machine
"Cluster-B" (ipadress: 192.168.0.183)
After creating the NLB-cluster we are able to ping from the remote-site "Department" to
the entire cluster: 192.168.0.185, 192.168.0.182 & 192.168.0.183
but we are NOT able to make a connection with RDP to those IP's. On the site
"Head-Office" RDP works fine.
if we remove the NLB-cluster on site "Head-Office", RDP from site "Department" to site
"Head-Office" (192.168.0.182 & 192.168.0.183) works fine again.
We tried RDP with NLB in multicast mode. This won't work either
Both sites connected with juniper firewalls and a juniper policy based VPN structure.
Overview:
Site "Head-Office" (192.168.0.0/24)
DFGW Juniper SSG5 (192.168.0.150)
Site "Department" (192.168.2.0/24)
DFGW Juniper SSG20 (192.168.2.10)
Cluster "RDS-Cluster" (192.168.0.185)
machine "Cluster-A" (192.168.0.182)
machine "Cluster-B" (192.168.0.183)
NLB-Settings:
Type: Unicast
Virtual IP: 192.168.0.185
Portrange: 3389 to 3389
Protocol: TCP
Affinity: None
I really hope you can help us out.
Thanks in advance!
September 22nd, 2010 10:42am
Please try the suggestions below first:
Terminal Services Client Cannot Connect to NLB Cluster TCP/IP Address
http://support.microsoft.com/kb/280805
If the issue still occur, check the following:
To use NLB, a computer must have:
-At least one network adapter for load balancing.
-Only TCP/IP used on the adapter for which NLB is enabled. Do not add any other protocols (for example, IPX) to this adapter.
-All hosts in the NLB cluster must reside on the same subnet.
-Ensure that the cluster's clients are able to access this subnet.
-All terminal servers in the terminal server farm should be joined to the same domain.
Do your server meet these requirements?
If they meet the requirement, please refer to the following article to check your configuration:
Network Load Balancing Step-by-Step Guide: Configuring Network Load Balancing with Terminal Services
http://technet.microsoft.com/en-us/library/cc771300(WS.10).aspx
Thanks.This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your
question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2010 6:22am