Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Windows Server 2008 R2 NLB cluster stops responding under a heavy load


View products that this article applies to.

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.

↑ Back to the top


Symptoms

Consider the following scenario:
  • You configure a Network Load Balancing (NLB) cluster on some computers that are running Windows Server 2008 R2.
  • The NLB cluster is under a heavy load.
In this scenario, the NLB cluster stops responding. You must forcibly restart all cluster nodes to recover from this issue.

↑ Back to the top


Cause

This issue occurs because an NLB-related function assumes that it is always called at the Deferred Procedure Call (DPC) level. However, this assumption is sometimes untrue. If the function is not called at the DPC level, a deadlock situation occurs in the NLB cluster.

↑ Back to the top


Resolution

To resolve the issue, install the following hotfix on all Windows Server 2008 R2 NLB cluster nodes in the affected NLB cluster.

Hotfix information

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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.21xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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
File nameFile versionFile sizeDateTimePlatform
Nlb.sys6.1.7600.21027340,99213-Aug-201103:41x64
Nlb.sys6.1.7601.21789340,99213-Aug-201103:35x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Nlb.sys6.1.7600.21027781,82413-Aug-201102:56IA-64
Nlb.sys6.1.7601.21789781,82413-Aug-201102:56IA-64

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_59313654de15d1c1c66cf8b2cc7c177c_31bf3856ad364e35_6.1.7601.21789_none_b2bf8f9d1675987d.manifest
File versionNot applicable
File size726
Date (UTC)13-Aug-2011
Time (UTC)08:46
PlatformNot applicable
File nameAmd64_e3908c085fe79d4b0709f7dc834315c7_31bf3856ad364e35_6.1.7600.21027_none_750423bef7027383.manifest
File versionNot applicable
File size726
Date (UTC)13-Aug-2011
Time (UTC)08:46
PlatformNot applicable
File nameAmd64_microsoft-windows-n..ncing-networkdriver_31bf3856ad364e35_6.1.7600.21027_none_0acb48084b064e1e.manifest
File versionNot applicable
File size2,669
Date (UTC)13-Aug-2011
Time (UTC)05:58
PlatformNot applicable
File nameAmd64_microsoft-windows-n..ncing-networkdriver_31bf3856ad364e35_6.1.7601.21789_none_0c72edf8485b611c.manifest
File versionNot applicable
File size2,669
Date (UTC)13-Aug-2011
Time (UTC)07:03
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_982654eeebf0ade578cab02df6e1987d_31bf3856ad364e35_6.1.7601.21789_none_25d9df1356c92bce.manifest
File versionNot applicable
File size724
Date (UTC)13-Aug-2011
Time (UTC)08:46
PlatformNot applicable
File nameIa64_ef06231f19aee06a657278010c162b67_31bf3856ad364e35_6.1.7600.21027_none_17aef50147de0179.manifest
File versionNot applicable
File size724
Date (UTC)13-Aug-2011
Time (UTC)08:46
PlatformNot applicable
File nameIa64_microsoft-windows-n..ncing-networkdriver_31bf3856ad364e35_6.1.7600.21027_none_aeae507a92a6e5e4.manifest
File versionNot applicable
File size2,667
Date (UTC)13-Aug-2011
Time (UTC)05:51
PlatformNot applicable
File nameIa64_microsoft-windows-n..ncing-networkdriver_31bf3856ad364e35_6.1.7601.21789_none_b055f66a8ffbf8e2.manifest
File versionNot applicable
File size2,667
Date (UTC)13-Aug-2011
Time (UTC)06:59
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbmdd, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2580504
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2014
Exists online : False
Views : 219