IPv6 network connectivity problems occur on a Windows Server 2008-based computer when the Network Load Balancing feature is enabled

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
When a static IPv6 IP address is configured on a network adapter, the subnet prefix length incorrectly changes from 64 to 128 on a Windows Server 2008-based computer. This problem occurs if the Network Load Balancing (NLB) feature is enabled. If Windows Server 2008 uses the IPv6 IP address over this network adapter, network connectivity problems occur.
Cause
This problem occurs because Windows Server 2008 removes the default IPv6 route when you bind the NLB or when the configuration changes on the NLB cluster node. Because Windows Server 2008 removes the default route, no appropriate route is found on the responding cluster node. Therefore, Windows Server 2008 drops some traffic that is destined for IPv6 dedicated IP addresses or for IPv6 virtual IP addresses on the NLB cluster.
Resolution
To resolve this problem, install the following hotfix on each cluster node in NLB.

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have the Network Load Balancing feature installed on the Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix. If you applied the hotfix while this node was an active part of the NLB cluster, after you apply the hotfix and restart the cluster node, check that the service is running and that the service start type is set correctly. To do this, follow these steps:
  1. Start a command prompt as administrator.
  2. Type sc query wlbs, and confirm that the state is RUNNING. If it is not, start the service by running the following:
    net start wlbs
  3. Type sc qc wlbs and confirm that the start type is SYSTEM_START. If it is not, set it to system by running the following command.
    sc config wlbs start= system
    Note There is a space before “system.”
  4. Open NLB Manager on the node, and then confirm that all nodes are converged. You might have to refresh the cluster state.
Note You should also follow these steps if the hotfix is uninstalled.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista and Windows Server 2008 file information notes
The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Nlb-unattend.exe6.0.6001.2237437,88811-Feb-200905:29x86
Nlbcfg.dll6.0.6001.2237466,56011-Feb-200905:30x86
Nlbmigplugin.dll6.0.6001.22374135,68011-Feb-200905:30x86
Nlbmprov.dll6.0.6001.22374102,40011-Feb-200905:30x86
Nlbmprov.mofNot Applicable8,37211-Feb-200900:52Not Applicable
Nlbmprovuninstall.mofNot Applicable13811-Feb-200900:52Not Applicable
Nlbtrace.mofNot Applicable2,39318-Dec-200721:11Not Applicable
Wlbsctrl.dll6.0.6001.2237480,38411-Feb-200905:30x86
Wlbsprov.dll6.0.6001.22374147,45611-Feb-200905:30x86
Wlbsprov.mofNot Applicable131,04411-Feb-200900:52Not Applicable
Wlbsprovuninstall.mofNot Applicable13811-Feb-200900:52Not Applicable
For all supported x64-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Nlb-unattend.exe6.0.6001.2237438,91211-Feb-200905:58x64
Nlbcfg.dll6.0.6001.2237478,84811-Feb-200905:59x64
Nlbmigplugin.dll6.0.6001.22374163,84011-Feb-200905:59x64
Nlbmprov.dll6.0.6001.22374122,36811-Feb-200905:59x64
Nlbmprov.mofNot Applicable8,37211-Feb-200900:47Not Applicable
Nlbmprovuninstall.mofNot Applicable13811-Feb-200900:47Not Applicable
Nlbtrace.mofNot Applicable2,39318-Dec-200721:11Not Applicable
Wlbsctrl.dll6.0.6001.2237493,18411-Feb-200905:59x64
Wlbsprov.dll6.0.6001.22374225,79211-Feb-200905:59x64
Wlbsprov.mofNot Applicable131,04411-Feb-200900:47Not Applicable
Wlbsprovuninstall.mofNot Applicable13811-Feb-200900:47Not Applicable
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Nlb-unattend.exe6.0.6001.2237481,92011-Feb-200904:45IA-64
Nlbcfg.dll6.0.6001.22374172,54411-Feb-200904:46IA-64
Nlbmigplugin.dll6.0.6001.22374347,13611-Feb-200904:46IA-64
Nlbmprov.dll6.0.6001.22374274,43211-Feb-200904:46IA-64
Nlbmprov.mofNot Applicable8,37210-Feb-200923:49Not Applicable
Nlbmprovuninstall.mofNot Applicable13810-Feb-200923:49Not Applicable
Nlbtrace.mofNot Applicable2,39318-Dec-200721:11Not Applicable
Wlbsctrl.dll6.0.6001.22374204,28811-Feb-200904:46IA-64
Wlbsprov.dll6.0.6001.22374461,82411-Feb-200904:46IA-64
Wlbsprov.mofNot Applicable131,04410-Feb-200923:49Not Applicable
Wlbsprovuninstall.mofNot Applicable13810-Feb-200923:49Not Applicable
Workaround
To work around this problem, add the default route on every NLB cluster node. You should take this action every time any configuration change occurs on the NLB cluster.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Package_for_kb963042_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42311-Feb-200916:39Not Applicable
Package_for_kb963042_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42211-Feb-200916:39Not Applicable
Package_for_kb963042_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42311-Feb-200916:39Not Applicable
Package_for_kb963042_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43011-Feb-200916:39Not Applicable
X86_microsoft-windows-n..kloadbalancing-core_31bf3856ad364e35_6.0.6001.22374_none_14b9ac19ea91bfc2.manifestNot Applicable30,46011-Feb-200905:55Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-n..kloadbalancing-core_31bf3856ad364e35_6.0.6001.22374_none_70d8479da2ef30f8.manifestNot Applicable30,78911-Feb-200906:22Not Applicable
Package_for_kb963042_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43111-Feb-200916:39Not Applicable
Package_for_kb963042_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43011-Feb-200916:39Not Applicable
Package_for_kb963042_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43111-Feb-200916:39Not Applicable
Package_for_kb963042_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43811-Feb-200916:39Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-n..kloadbalancing-core_31bf3856ad364e35_6.0.6001.22374_none_14bb500fea8fc8be.manifestNot Applicable30,76811-Feb-200905:06Not Applicable
Package_for_kb963042_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42711-Feb-200916:39Not Applicable
Package_for_kb963042_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43411-Feb-200916:39Not Applicable
clusters; clustering; nlb; network load balancing; ipv6; DIP; VIP; dedicated IP; virtual IP;
Properties

Article ID: 963042 - Last Review: 01/15/2015 19:30:51 - Revision: 4.0

Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Server 2008 Standard without Hyper-V, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 Datacenter without Hyper-V

  • kbnosurvey kbarchive kbautohotfix kbexpertiseinter kbfix kbbug kbsurveynew kbqfe KB963042
Feedback