Select the product you need help with
IPv6 network connectivity problems occur on a Windows Server 2008-based computer when the Network Load Balancing feature is enabledArticle ID: 963042 - View products that this article applies to. On This PageSYMPTOMSWhen 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. CAUSEThis 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. RESOLUTIONTo resolve this problem, install the following hotfix on each cluster node in NLB. Hotfix informationA 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
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. PrerequisitesTo apply this hotfix, you must have the Network Load Balancing feature installed on the Windows Server 2008-based computers.Restart requirementYou 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:
Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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 notesThe .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 2008Collapse this table
For all supported x64-based versions of Windows Server 2008 and Windows VistaCollapse this table
For all supported IA-64-based versions of Windows Server 2008Collapse this table
WORKAROUNDTo 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. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONAdditional file information for Windows Server 2008 and Windows VistaAdditional files for all supported x86-based versions of Windows Server 2008 and Windows VistaCollapse this table
Additional files for all supported x64-based versions of Windows Server 2008 and Windows VistaCollapse this table
Additional files for all supported IA-64-based versions of Windows Server 2008Collapse this table
PropertiesArticle ID: 963042 - Last Review: October 7, 2011 - Revision: 3.0 APPLIES TO
|



Back to the top








