Services and applications that are affected by high load require technologies to address this issue. Network Load Balancing is a technology that allows system administrators to configure clusters that distribute traffic between several servers. In this article, I will show you how to Configure Network Load Balancing on Windows Server. Please see How to Setup Public Load Balancer in Azure, How to Create a load balancer for Azure Stack Hub, How to disable power plan in Windows via GPO and Windows,

Suppose you have a website that receives a large number of requests and cannot be handled by one server.

In this case, you would configure a NLB cluster to distribute traffic across multiple web servers and thus ensuring that the website can serve all requests.

Also, see how to configure a remote server (windows) to Support Ansible, and how to deploy Azure VMware solution private cloud, how to fix Failover Cluster Manager failed while managing one or more clusters, the error was unable to determine if the computer exists in the domain.

Add Network Load Balancing Role on Windows Server

Open your VM server manager and then select Add Roles and Features.

Then click Next. Please see the steps in Deploying a load balancer from scratch and adding backend servers.

Click Next.

Select your server name from the server pool and then click Next.

Check the WEB Server (IIS) roles box, click add features, then select Next.

Check the Network Load Balancing box, click add features, then select next.

Now, click Next.

Click Next.

Click Install.

Configuring Network Load Balancing in Windows Server 2019 After installing the Network Load Balancing feature on all the participating NLB nodes, the subsequent step is to configure Network Load Balancing. For this, you would like to perform the subsequent steps.

Please see how to manage azure resource manager resource groups by using Azure CLI, and how to configure azure resources with tools. Also, see how to install and configure Ansible on Ubuntu.

Create a New Cluster

On the Server Manager console of the SRV2019-1 NLB node. Click Tools and then choose Network Load Balancing Manager.

Right-click Network Load Balancing Clustering and then choose New Cluster

On the New Cluster: Connect panel, type SRV2019-1.techdirect.local (or IP Address) in the Host field then click Connect. Verify that the Interface name is listed then click next.

On the New Cluster, set the priority (unique host identifier) value 1. This NLB node will reply to the clients’ queries, first, also ensure that the default status has set as Started and click next.

Click the Add button to add a new Cluster IP address.

PS Note: The Cluster IP address is the new virtual IP address on which the host service, during this case, IIS will run.

Type Cluster IP Address such as 10.0.0.100 and click ok.

Then click Next.

On the New dialog box, Select a cluster operation mode, Unicast and then click next.

Then click Finish

Then wait until the SRV2019-1 NLB node is added successfully. The Icon Color of the added NLB node should be green.

Right-click on the Cluster name and then select Add Host to Cluster.

Connect dialog box, type SRV2019-2, and then click Connect to add one more NLB node, and click next.

On the Add Host to Cluster Dialog box: Host Parameters dialog box, set the priority value as 2 and proceed to next.

Then click Finish

Finally, verify that the second NLB node SRV2019-1 is added successfully.

Please see how to install Ansible on Windows with Cygwin, how to automate infrastructure deployments in the cloud with ansible and azure pipelines, and how to install Kerberos packages in Windows via Cygwin.

Verifying Network Load Balancing Configuration

To verify that your NLB Cluster is configured successfully and functioning properly, perform the subsequent steps. Type 10.0.0.100 within Internet Explorer and verify that you simply are ready to access the Default Webs

Close Internet Explorer. On the SRV2019-1 node. Then open the Network Load Balancing Manager window, select and right-click SRV2019-1(Ethernet), select Control Host and then select Stop to stop this node temporarily.

Then switch back to SRV2019-DC and try again to open the Default Website. the Default Website should still be displayed. However, this time, the SRV2019-2 NLB node will serve the Website.

I hope you found this article useful on how to Configure Network Load Balancing In Windows Server. Please let me know in the comment section if you have any questions.