You configure a Network Load Balancing (NLB) cluster by using some computers that are running Windows Server 2008 R2.
A cluster membership change starts the convergence process. For example, assume that a node is added or that a cluster is partitioned, and then the convergence process starts.
In this scenario, some NLB nodes remain in the converging state and cannot accept connections. Additionally, the following event log is added to the System log:
Source: NLB Logged: <Time> Event ID: 119 Task Category: None Level: Warning Keywords: User: N/A Computer: <computer name> Description: NLB cluster [<IP or host name>]: The NLB driver has detected an inconsistency in the Extended Affinity configuration between cluster host <ID> and cluster host <ID>. A client IP address is on the Extended Affinity exception list on both hosts. You should run the Powershell cmdlet ‘Set-NlbClusterNode-Reload’ followed by ‘Start-NlbClusterNode’.
Note When this issue occurs, the Network Load Balancing Manager window or another monitoring tool reports that the state of the problematic node is in the converging state.
This issue occurs because both of the NLB nodes incorrectly enter into an infinitely converging state.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, your computer must be running Windows Server 2008 R2. Additionally, the Network Load Balancing (NLB) feature must be installed.
You do not have to restart the computer after you apply this hotfix.
Restart the Windows load balancing service (WLBS) that hosts the Nlb.sys module by running the following sequence of commands:
net stop wlbs
net start wlbs
If you uninstall this hotfix, restart the computer or restart the service.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
To work around this issue, restart the problematic NLB nodes.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The following event is logged after you install this hotfix if the NLB diagnostic log is enabled: