Ok so here is my dilema. I have two terminal servers on different subnets (different locations). I want to use NLB to load balance traffic and for fail over, applying updates ect. Now the two subnets are connected with two wan switches using static routes.
Here is what I set up
Terminal Server 1:
NIC 1
Host IP address: 172.16.8.9 /21
Gateway: 172.16.15.254
DNS:172.16.16.1/172.16.16.2
NIC 2
Host IP address: 172.16.8.10 /21
Cluster IP address: 172.16.8.15 /21
NLB Mode: Unicast
Port Rule: all opened
Name resolution: Termserver.domain.com
Priority:1
TCP/IP advanced
Additional IP: 172.16.8.15
Terminal server 2
NIC 1
Host IP address: 172.16.16.9 /21
Gateway: 172.16.23.254
DNS:172.16.16.1/172.16.16.2
NIC 2
Host IP address: 172.16.16.10 /21
Cluster IP address: 172.16.8.15 /21
NLB Mode: Unicast
Port Rule: all opened
Name resolution: Termserver.domain.com
Priority: 2
TCP/IP advanced
Additional IP: 172.16.8.15
Now terminal server one appears fine but server two has no network connectivity outside of its subnet.
I tried adding an addition cluster IP 172.16.16.15 /21 assigned this as the cluster ip for server two. Added it as an additional IP on both servers. But then neither server could communicate outside of it subnet. I did kind of expect this.
I then tried removing 172.16.8.15 from server 2 additional IP and 172.16.16.15 from server 1 additional IP. Now both servers could see the entire network (all subnets). But NLB doesn't work as this is now two seperate clusters due to two seperate IP's.
I've always been under the impression this could work but I see no way of making it work. Unless I put both servers on the same site however this kind of defeats the object of load balancing accross the WAN. All help welcome.
Bookmarks