NLB for terminal server not working
Posted on 2011-09-27
I have 3 win 2k3 servers that I want to use NLB as a terminal server farm. These are all VMs on vsphere, and I know that shouldnt make much of a difference.
I was going to use multicast, as that seemed to be the best way.
I installed NLB on each server, then set the cluster IP and the cluster name on each, set them to multicast, and then set the priority.
The MAC it shows seems to be the same for 2 of the machines, and the 3rd is different. After I added this to the 3 machines, when I connect to the cluster, only 1 allows connections, when I look at the other 2, it states acquiring network address. It gives an IP Conflict message,
I did add (as per the insructions I saw) the cluster IP into each server as a 2nd IP after installing the NLB.
I ended up having to turn off the NLB from 2 of the machines, and let just one of them keep the cluster IP so people could still connect to it. I am not certain of what is going wrong. I was able to ping each of the servers actual IP address, and could reach each via RDP before the NLB config.
I have a cisco 3750 switch, and I did add an static arp statement, which pointed to what I assume was the cluster MAC, each server showed the same MAC for the most part, but one had 01, and 2 had 02 as the first characters in the MAC. I used what they gave, but replaced the first 2 characters with 00 for the arp statement.