So moving on, let's enable Windows Network Load Balancing.
So the first thing we need to do on the first VPN server is
install the Network Load Balancing role,
and the way to do that is with PowerShell because it's quick and simple,
and the command is just Install‑WindowsFeature NLB and
‑IncludeManagementTools as well.
Once that's done, we can move on with the configuration of NLB.
Now in the interest of time,
I've already installed the NLB feature on my second VPN server here.
So I'm just going to open up the Network Load Balancing management console,
and the configuration is actually pretty straightforward.
So we're just going to right‑click here and choose New Cluster,
and we'll provide the name of the first server,
that's this individual server, and you can use its host name,
or if you're on the server itself, you can just use localhost.
And if you have multiple network interfaces,
you only need to deploy NLB on the external interface.
So if you're using a single NIC, or single network interface,
then you can just select the only available adapter here,
but if you're using the multi‑home model,
simply select the external interface and then choose Next.
No other changes here.
This is the dedicated IP address of this server, and so we'll click Next.
And here's where you're going to add your cluster IP address,
and this is the virtual IP address or VIP for this cluster.
So make sure that this is an IP address from the same subnet as the VPN server,
and of course, obviously,
make sure it's not in use anywhere else on your network.
So we'll click OK, click Next.
And this is the operating mode that I was talking about before.
In this case,
we're going to use Unicast because that's kind of
the best default operating mode.
You may have to use Multicast, depending on your hypervisor,
but in this case, we're just going to go use Unicast and move on.
Switch is next, and here we're just going to accept the defaults.
We're going to go ahead and cluster this for all ports on this server.
It's not really important that we set this up for individual ports.
The edge firewall is going to do the screening of ports.
So in this case, we'll go ahead and load balance all ports on
that external interface, and then we'll click Finish, and once
the configuration is complete,
you'll see that the interface here turns green. At this point, we're
ready to install our second node in the cluster, and to do that, I'm
actually just going to right‑click on this and choose Add Host To
Cluster, and once again, as a reminder,
I've already installed the NLB feature or role on the second server.
So now I'll add the host name of the second server here, and once again, I'm
going to choose the external interface, and choose Next,
choose Next again, and then Finish.
So then once the cluster is complete,
you should see two healthy VPN servers here.
The status showing as Converged, meaning the Network Load Balancing
configuration has been propagated to both servers. And at this point,
you should now be able to update the NAT rule on your edge firewall and
deliver that traffic to the virtual IP address, here in my case,
192.168.1.235, and through the magic of Network Load Balancing,
it will distribute the traffic to the nodes in the cluster, and load balancing will be set up.