- Open NETWORK CONNECTIONS folder.
- Press ALT key to bring up the menu bar, go to ADVANCED menu
- Select Advanced Settings
- Under Adapters and Binding section, reorder positions of NIC interfaces to make sure NLB is the first interface and other network interface is second.
3. Close Wizard when Network Load Balancing Manager is installed.
4. On CAS1 server select START > Administrative Tools > Network Load Balancing Manager
5. When NLB Console will start, right click on Network Load Balancing Cluster and select New Cluster.
6. On New Cluster: Connect screen, type FQDN for CAS1 server e.g. CAS1.katwal.local and select Connect.
7. Select Network Interface with IP 10.0.0.10 and select Next button.
8. On New Cluster:Host Parameters windows select all default and select Next.
9. On New Cluster: Cluster IP addresses window select ADD button and add IPv4 IP address of NLB cluster which is 10.0.0.50 with subnet mask of 255.0.0.0, select OK, select NEXT
10. On New Cluster: Cluster Parameters window under Full Internet Name section type the URL name selected above: mail.katwal.local
11. Leave Cluster Operation Mode to be set to Unicast and select NEXT.
12. On Add/Edit Port Rule window, select Finish.
13. Allow some time for cluster to converge and turn into green colour icon.
14. Now log on to CAS2 server and use PING command to check if mail.katwal.local replies back on IP address that was assigned to NLB (10.0.0.50).
15. Just in case there is some issue with getting the reply back, check DNS Server configuration.
16. To add CAS2 server to the NLB Cluster open NLB Manager Console
17. Right Click on the cluster (mail.katwal.local) and select Add Host To Cluster.
18. In Host Field type FQDN for CAS2 server (CAS2.katwal.local) and select Connect.
19. Select NLB interface with IP address of 10.0.0.11 and select Next, Next.
20. Leave everything to default as we did earlier and select Finish.
21. Now you should see second node of CAS2 will start to converge just as CAS1 did earlier and you should see it with the green icon.
22. Verify that when one of the nodes is turned off from NLB Manager we can still get reply for URL (mail.katwal.local) from IP address 10.0.0.50. Additional test will be to turn of both nodes from NLB manager and check if we cannot get to mail.katwal.local and then start only one node at a time.
23. If using virtual machines you may want to have static MAC address that was provided when cluster was configured. You can get to it by using NLB manager and get to to the properties of Cluster and selecting Cluster Parameter tab. Once you have the MAC address if you are using VMWARE you can go to the properties of NIC we used for NLB and add the MAC address for making it static. Similarly in Hyper-V Manager configure NIC used for NLB and fill in info under Static section. on Hyper-V also select Enable Spoofing of MAC Addresses.
24. To confirm changes to NIC have not broken anything restart both nodes one at a time and confirm that both nodes converge without issues.
25. Next step is to make sure NIC forwarding is done so that all OWA requests only go to NIC selected for NLB. Following is example of the command I ran on both of my CAS servers.