Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We had a 2 node NLB cluster running IIS websites on virtual machines. Both nodes were online, the balancer functioned exactly as expected, (if traffic is 50/50 balanced, and you stop or drainstop a node, all traffic routes seamlessles to the other node.)

But when I rebooted a node, even if I stopped it prior to reboot, the OTHER node which should be receiving production traffic during the reboot stopped accepting requests.

To my knowledge this was NOT how NLB is supposed to work. If I power down a node, the other nodes in the NLB cluster shouldn't care, and should continue to accept traffic according to their port rules while the offline node reboots.

None of my port rules employed affinity, so I knew that wasn't the issue.

So after agonizing over it a bit, I stumbled on the answer (see my posted answer)

share|improve this question

After some research, I’ve discovered that the issue is related to VMWare and the fact that the NLB cluster is in Unicast mode.

Apparently VMWare has to be configured properly to avoid issues at the switch level with virtual MAC addresses that are created from Unicast mode NLB clusters, and recommends configuring the NIC’s to accommodate the mode, or better yet, simply use NLB clusters in Multicast mode to avoid the issue entirely.

NLB Unicast Clusters & VMWare

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.