2 node DirectAccess 2012 R2 NLB cluster where the first node doesn't automatically start nlb on a server restart RRS feed

  • Question

  • Hi, I in the process of finishing off a 2 node DA cluster and I'm finding that my second NLB node is doing everything by the text book but the first NLB node is not automatically starting its High Availability service within the NLB cluster. To start this I need to go into the NLB mmc and click start on both the internal and external interfaces of this node.

    I have check the logs and can't see any reason why the second node starts this automatically yet the first node doesn't. The servers appear to be on slow hardware but if it was a timing issue I would have expected to have seen an error in the event logs.

    Has anyone else seen this and can point me to the area that could be causing this issue?

    Tuesday, August 23, 2016 9:25 AM

All replies

  • This is a know issue. When you click on the Virtual IP Address trough NLB Manager you can select the properties. There is also a settings that tells you what mode it should be in after resume. Most often it is set to "Stopped". You set it to "Started".

    Boudewijn Plomp | Conclusion FIT

    Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer". This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, October 27, 2016 7:18 AM