Source: http://support.microsoft.com/?id=812870
Article ID : 812870 Last Review : November 9, 2004 Revision : 4.0
When you run the WLBS display command or the WLBS query command on a Network Load Balancing cluster host, you receive results that indicate that the cluster host is not converging successfully, or that the cluster is converging only with itself. For example, you may receive results that are similar to one of the following:
WLBS Cluster Control Utility V2.4 (c) 1997-2003 Microsoft Corporation.Cluster 192.168.192.4Host 2 has entered has entered a converging state 1 time(s) since joining the cluster and is still in a state of convergence.Host 2 converging with the following host(s) as part of the cluster:1
WLBS Cluster Control Utility V2.4 (c) 1997-2003 Microsoft Corporation.Cluster 192.168.192.4Host 2 has entered has entered a converging state 1 time(s) since joining the cluster and is still in a state of convergence.Host 2 converging with the following host(s) as part of the cluster:
WLBS Cluster Control Utility V2.4 (c) 1997-2003 Microsoft Corporation.Cluster 192.168.192.4Host 2 has entered has entered a converging state 1 time(s) since joining the cluster and is still in a state of convergence.Host 2 converged as DEFAULT with the following host(s) as part of the cluster:2
Make sure that you are not using a crossover cable between the private network adapters in the cluster.
If you use a layer 2 switch to connect the Network Load Balancing hosts in unicast mode, make sure that you can pass broadcast packets. If this feature is not enabled, the heartbeat packets cannot be detected by other hosts. This causes the hosts to converge only with themselves.
Replace the switch that connects the private network adapters in the cluster with a hub. Connect the hub to the uplink port on the switch. If you already use a hub to connect the private network adapters, set the MaskSourceMAC registry value to 0 (zero).
If the cluster hosts have Gigabit network adapters, verify that they are listed on the hardware compatibility list (HCL).
Check the Gigabit Server Adapter properties. The network adapter driver may prevent hosts from overwriting the real Media Access Control (MAC) address with the address that is used for Network Load Balancing (the ClusterNetworkAddress entry that is returned when you run the WLBS display command). This MAC address is in the format of 02-BF-ww-xx-yy-zz where ww-xx-yy-zz is the cluster virtual IP address in hexadecimal notation. For example, 02-BF-0A-A5-02-13 corresponds to IP address 10.165.2.19.
If you are using Network Load Balancing in unicast mode, you may have to manually set the network adapter's Locally Administered Address (LAA) to the Network Load Balancing cluster unicast MAC address (ClusterNetworkAddress). You must do this by using the driver program for the load-balanced network adapter on each host in the cluster. You must not set the LAA for Network Load Balancing clusters that are operating in multicast mode.
Make sure that you are not using fault tolerant or teaming network adapters. If you are using teaming network adapters, disable teaming mode for the duration of the troubleshooting process.