Article ID: 323437 - Last Review: December 3, 2007 - Revision: 7.5 How To Configure Network Load Balancing Parameters in Windows Server 2003This article was previously published under Q323437 On This PageSUMMARY This step-by-step article describes how to configure
Network Load Balancing parameters in Windows Server 2003. You can use Network Load Balancing to spread incoming requests across as many as 32 servers. You can do so to expand enterprise-wide services, such as Web servers, Terminal Services, and streaming-media servers. Network Load Balancing also makes sure that your servers respond quickly, even under heavy loads. It does this by automatically detecting when a server stops working, and then quickly reassigning client traffic among the remaining servers. This safeguard can help you provide uninterrupted, continuous service for your critical business programs. Configure Network Load Balancing ParametersTo configure Network Load Balancing parameters, you must configure the cluster parameters, host parameters, and port rules.For additional information about how to set up TCP/IP for Network Load Balancing, click the article number below to view the article in the Microsoft Knowledge Base: 323431
(http://support.microsoft.com/kb/323431/EN-US/
)
How To Set Up TCP/IP for Network Load Balancing in Windows Server 2003
Configure Cluster Parameters
For additional information about the use of Remote Control in Network Load Balancing, see the "Network Load Balancing parameters: Network Load Balancing Clusters" Windows Server 2003 Help and Support Center topic. Configure Host Parameters
To make sure that Network Load Balancing Manager is displaying the most recent host information, right-click the cluster, and then click Refresh. You must do so because the host properties that Network Load Balancing Manager displays are a copy of the host properties that were configured the last time Network Load Balancing Manager connected to that host. When you click Refresh, Network Load Balancing Manager reconnects to the cluster and displays updated information. NOTE: You can also open the Network Load Balancing Properties dialog box through the Network Connections tool. However, Network Load Balancing Manager is the preferred method. If you use the Network Connections tool, you must make the same configuration changes on every cluster host. Using both Network Load Balancing Manager and the Network Connections tool together to change Network Load Balancing properties may create unpredictable results. The parameters that are set in the Network Load Balancing Properties dialog box are recorded in the registry on each host. Changes to Network Load Balancing parameters are applied when you click OK in the Network Load Balancing Properties dialog box. Clicking OK stops Network Load Balancing (if it is running), reloads the parameters, and then restarts cluster operations. Configure Port RulesBefore you continue, review the "Port Rules" section of the "Checklist: Enabling and configuring Network Load Balancing" Windows Server 2003 Help and Support Center topic. Without a complete understanding of the topics that are addressed in this section, you cannot properly configure port rules.Configuring port rules includes the creation, editing, and removal of port rules. To create port rules:
If a host tries to join the cluster with a different number of rules, or with different rules from the other hosts, it is not accepted as part of the cluster. The rest of the cluster then continues to handle the traffic as before. At the same time, a message is entered into the Windows event log. When this occurs, see the Event log to determine which host is in conflict with the other cluster hosts, resolve the conflict, and then restart Network Load Balancing on that host. To allow Network Load Balancing to properly handle IP fragments, avoid using None when you select UDP or Both for your protocol setting. NOTE: When you are using Network Load Balancing Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. As a security best practice, consider using "Run as" to perform this procedure. If you are configuring a cluster or host by running Network Load Balancing Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. You can also open the Network Load Balancing Properties dialog box through the Network Connections tool. However, Network Load Balancing Manager is the preferred method. If you use the Network Connections tool, you must make the same configuration changes on every cluster host. Using both Network Load Balancing Manager and the Network Connections tool together to change Network Load Balancing properties may lead to unpredictable results. If all your hosts are running a product in Windows Server 2003, you can specify port rules to apply to only specific IP addresses. This is useful when you create virtual clusters. If you are not running Windows Server 2003, you must apply the port rules to all IP addresses. For more information about virtual clusters, see "Understanding Virtual Clusters". The list of all currently installed port rules is sorted by port range. The parameters that are set in the Network Load Balancing Properties dialog box are recorded in the registry on each host. Changes to Network Load Balancing parameters are applied when you click OK in the Network Load Balancing Properties dialog box. Clicking OK stops Network Load Balancing (if it is running), reloads the parameters, and then restarts cluster operations. If you are working from a computer that has a single network adaptor that is bound to Network Load Balancing in Unicast mode, you cannot use Network Load Balancing Manager on this computer to configure and manage other hosts because a single network adapter in Unicast mode cannot have intra-host communication. However, you can communicate with computers that are outside the cluster. To make sure that Network Load Balancing Manager is displaying the most recent host information, right-click the cluster, and then click Refresh. You must do so because the host properties that Network Load Balancing Manager displays are a copy of the host properties that were configured the last time Network Load Balancing Manager connected to that host. When you click Refresh, Network Load Balancing Manager reconnects to the cluster and displays updated information. Enable Multicast Support
NOTE: When you are using Network Load Balancing Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. As a security best practice, consider using "Run as" to perform this procedure. If you are configuring a cluster or host by running Network Load Balancing Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. You can also open the Network Load Balancing Properties dialog box through the Network Connections tool. However, Network Load Balancing Manager is the preferred method. If you use the Network Connections tool, you must make the same configuration changes on every cluster host. Using both Network Load Balancing Manager and the Network Connections tool together to change Network Load Balancing properties may lead to unpredictable results. You can only enable IGMP support when your cluster is configured for multicast mode. If you enable IGMP support, the permitted multicast IP address is restricted to the standard class D range. This is 224.0.0.0 to 239.255.255.255. Enable Internet Group Management Protocol (IGMP) Support
NOTE: When you are using Network Load Balancing Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. As a security best practice, consider using "Run as" to perform this procedure. If you are configuring a cluster or host by running Network Load Balancing Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. You can also open the Network Load Balancing Properties dialog box through the Network Connections tool. However, Network Load Balancing Manager is the preferred method. If you use the Network Connections tool, you must make the same configuration changes on every cluster host. Using both Network Load Balancing Manager and the Network Connections tool together to change Network Load Balancing properties may lead to unpredictable results. You can only enable IGMP support when your cluster is configured for multicast mode. If you enable IGMP support, the permitted multicast IP address is restricted to the standard class D range. This is 224.0.0.0 to 239.255.255.255. Manage Existing Clusters from Network Load Balancing Manager by Using a Host List
NOTE: To run Nlb.exe from a remote computer, you must enable remote control on the host that is running Network Load Balancing. The Network Load Balancing remote control option presents many security risks. Only use remote control on a secure computer inside your firewall. Because of the many security risks remote control presents, Microsoft recommends that you do not enable the remote control feature. Instead, use other remote management tools such as Network Load Balancing Manager or Windows Management Instrumentation (WMI). When you are using Nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. As a security best practice, consider using "Run as" to perform this procedure. If you are configuring a cluster or host by running Nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. To view the complete syntax for this command, type nlbmgr /help at a command prompt, and then press ENTER. Make sure that only users in the local Administrators group have access to the host list file. You can include comments in the host list by preceding the comment with a semicolon (;). You can use this procedure to connect to multiple hosts and all Network Load Balancing clusters on those hosts. The clusters and hosts are then displayed in Network Load Balancing Manager. This is particularly useful when a host's Network Load Balancing network adapter is having connectivity problems, but another network adapter is available on that host. You can also use this procedure to detect and diagnose problems such as cluster hosts that are converging separately. TroubleshootingThe number and type of rules must be exactly the same for each host in the cluster. If a host tries to join the cluster with a different number of rules from the other hosts, it is not accepted as part of the cluster, and the rest of the cluster continues to handle the traffic as before. At the same time, a message is logged in the Windows Event log. If this occurs, view the Event log to determine which host is in conflict with the other cluster hosts, resolve the conflict, and then restart Network Load Balancing on that host.You must also add the cluster IP address or addresses to the TCP/IP settings of the local area connection:
APPLIES TO
| Article Translations
|
Back to the top
