Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 have a 2 node NLB cluster. I recently added more IP's to the cluster range, after which point, the NLB NIC's on both of my nodes ended up in a permanent "acquiring network address" state.

The cluster appears to be functioning despite this hang in acquiring an address.

We've also rebooted the machines, and these NIC's remain in this state "acquiring network address" even after reboot, which I find troubling.


  1. Does anyone know where I can find documentation on how NLB binds to a NIC? (are there dll's involved, drivers, etc.)
  2. Does anyone know of any programs that have known incompatability issues with NLB?

We have an application server installed on these NLB nodes (AOL Server) that interacts with the NIC's as well, and I suspect that it might be causing this issue. Before I go directly to Microsoft, I want to gather as much information as possible about the issue.

Any help / guidance would be much appreciated...

share|improve this question

Your Answer


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

Browse other questions tagged or ask your own question.