[an error occurred while processing this directive]
Use the following procedure to connect to a Network Load Balancing (NLB) cluster by typing the name of a single host. After you select a particular cluster, that cluster and all the hosts in the cluster will be displayed in NLB Manager.
You can also perform the task described in this procedure by using Windows PowerShell. For more information about using Windows PowerShell for NLB clusters, see http://go.microsoft.com/fwlink/?LinkId=140180.
When you are using Network Load Balancing (NLB) 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. If you are configuring a cluster or host by running NLB 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.
|To connect to existing Network Load Balancing clusters by using a single host|
To open NLB Manager, click Start, click Administrative Tools, and then click Network Load Balancing Manager. You can also open NLB Manager by typing Nlbmgr at a command prompt.
Right-click Network Load Balancing Clusters, and then click Connect to Existing.
Type the name of one of the cluster hosts, and then click Connect. The NLB clusters that exist on that host will be listed at the bottom of the dialog box.
Click the cluster name that you want to manage from NLB Manager, and then click Finish.
When using this procedure, certain network problems can prevent NLB Manager from connecting to one or more of the other hosts in the cluster. Similarly, if you have misconfigured the cluster by using duplicate priorities on multiple hosts, NLB Manager will not be able to connect to those misconfigured hosts. In these cases, some hosts will not appear in NLB Manager.
If all of the hosts do not appear in NLB Manager, try using a host list instead. See Connect to Existing Network Load Balancing Clusters by Using a Host List. In addition, information is available in the Windows event log to diagnose this issue on one or more of the cluster hosts.