Remote query returns an incorrect name after you change the computer name on an NLB cluster member

When you run a remote query to obtain the names of the members of a Network Load Balancing cluster, an incorrect computer name may be returned.

This issue may occur if you change the host name of the cluster member.

When you change the name of a cluster member (and then restart that member when prompted), the remote WLBS query cluster IP address command returns the previous host name of the Network Load Balancing member server.

To work around this issue, run the WLBS reload command to reload the fully qualified domain name (FQDN) of the host computer.

Note When you restart the computer, this also reloads the FQDN of the host computer.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

To increase security in Windows Server 2003, the Network Load Balancing remote control management feature has been revised to use identity heartbeats, which are independent from the normal Network Load Balancing heartbeat traffic. Identity heartbeats are exchanged between hosts and contain the following information:

�	The host ID
�	The dedicated IP address
�	The FQDN of the sender

This information is cached and provided to the user when a query is made for all members of the Network Load Balancing cluster. The FQDN is obtained from the TCP/IP portion of the Windows registry. The issue described in the "Symptoms" section of this article occurs because the Network Load Balancing driver is not updated with the new name information after you rename and restart the computer. The driver reads the name information when it binds to the network adapter (including whenever Windows starts) and whenever an explicit reload request is issued (WLBS reload). However, when you restart the computer after you change the computer name, the TCP/IP Windows registry location does not contain the updated name information until after the Network Load Balancing driver loads the information from the registry.

For additional information about Windows Server 2003 Network Load Balancing, visit the following Microsoft Web sites: