Web Servers - Do you know how to Setup NLB on Windows Server 2016? (aka Network Load Balancing)

Last updated by StevenAndrews about 4 years ago.See history

Downtime occurs when you have a single server setup.

TODO: This is 2008 R2 – update to 2016 Note: 2008 R2 was not as reliable as later versions. So it would be better to use failover cluster in Server 2012 R2 or 2016 for a more reliable infrastructure configuration.

Use NLB to allow load balancing and failover. On each of your Windows Servers, you will host your website.

You need to follow these steps to get it up and running:

  1. On all nodes of the NBL cluster, the Network Load Balancing Feature needs to be installed.
    Setup NLB
    Figure: Install the NLB Feature
  2. Open the Network Load Balancing Manager from Administrative Tools
    Setup NLB
    Figure: Under the Cluster menu item, click New
  3. Enter the first node in the cluster in ‘Host’ and press ‘Connect’
    Setup NLB
    Figure: Select the interface for the node
  4. Enter a Priority as 1 (this is just a host identifier)
    Setup NLB
    Figure: In 'Priority' enter '1'
  5. NLB55
    Setup NLB
    Figure: Enter a virtual IP address for the cluster. eg.
  6. Choose the IP address of your cluster from the dropdown list Set a Full Internet Name eg. spcluster.sydney.ssw.com.au. Ensure the Multicast Cluster operation mode is selected.
    Setup NLB
    Figure: Set the 3 cluster parameters
  7. You want sticky sessions so you don’t mistakenly bounce between servers (and lose your state)
    Setup NLB
    Figure: Leave the Port Rule as default. This will provide sticky session
    Setup NLB
    Figure: Success. The cluster configuration will show a green icon
  8. Right click the name of the cluster eg. spcluster.sydney.ssw.com.au Click Add Host To Cluster
    Setup NLB
    Figure: Add the 2nd web server with a priority of 2
  9. Open a command prompt and type in wlbs query to verify the cluster:
    Setup NLB 13
    Setup NLB
    Figure: Type in wlbs query to verify the cluster
  10. Ping both nodes and the virtual IP address externally to verify they are all working
We open source. Powered by GitHub