Third-party vendors may be unable to achieve IPv6 Ready Logo Phase-2 certification in Windows Server 2003

Article translations Article translations
Article ID: 950092 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • A computer that is running Windows Server 2003 ("Computer A") sends a ping command to another Windows Server 2003-based computer ("Computer B") by using the IPv6 protocol.
  • Computer B responds to the ping command by sending a Neighbor Advertisement packet. Then, a neighbor cache entry (NCE) is created on Computer A. In this situation, the NCE is marked as "reachable." It will be marked as "stale" in 30 seconds.
  • Before the 30 seconds elapse, Computer A receives another Neighbor Advertisement packet. This packet has a different link-layer address than the previous packet that was sent from Computer B. Additionally, the "Solicited" flag is set and the "Override" flag is cleared in the new Neighbor Advertisement packet.
In this scenario, the system silently ignores the new Neighbor Advertisement packet instead of marking the created NCE as "stale."

This behavior does not comply with the RFC 4861 specifications. Therefore, third-party vendors may be unable to achieve IPv6 Ready Logo Phase-2 certification.

RESOLUTION

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 this specific problem. 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.

After you apply this hotfix, the system handles Neighbor Advertisement packets in compliance with the RFC 4861 specifications. The system sets the NCE state to "stale" by using a different layer address after it receives the new Neighbor Advertisement packet.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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 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 Server 2003 with Service Pack 1, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
6to4svc.dll5.2.3790.277199,84016-Aug-200614:01x86SP1
Tcpip6.sys5.2.3790.3119225,98411-Apr-200812:39Not applicableSP1
Windows Server 2003 with Service Pack 2, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpip6.sys5.2.3790.4271234,49611-Apr-200812:54Not applicable
Windows Server 2003 with Service Pack 1, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
6to4svc.dll5.2.3790.2771362,49611-Apr-200820:46IA-64SP1Not applicable
Tcpip6.sys5.2.3790.3119736,89611-Apr-200820:46Not applicableSP1Not applicable
W6to4svc.dll5.2.3790.277199,84011-Apr-200820:46x86SP1WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpip6.sys5.2.3790.4271764,54411-Apr-200821:42Not applicable
Windows Server 2003 with Service Pack 1, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
6to4svc.dll5.2.3790.2771124,41611-Apr-200820:49x64SP1Not applicable
Tcpip6.sys5.2.3790.3119362,75211-Apr-200820:49x64SP1Not applicable
W6to4svc.dll5.2.3790.277199,84011-Apr-200820:49x86SP1WOW
Windows Server 2003 with Service Pack 2, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpip6.sys5.2.3790.4271375,68011-Apr-200821:44x64
Windows XP Professional with Service Pack 1, x64-based editions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
6to4svc.dll5.2.3790.2771124,41611-Apr-200820:49x64SP1Not applicable
Tcpip6.sys5.2.3790.3119362,75211-Apr-200820:49x64SP1Not applicable
W6to4svc.dll5.2.3790.277199,84011-Apr-200820:49x86SP1WOW
Windows XP Professional with Service Pack 2, x64-based editions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpip6.sys5.2.3790.4271375,68011-Apr-200821:44x64

STATUS

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

MORE INFORMATION

To align with the IPv6 Ready Logo Phase-2 certification process, third-party vendors must also apply hotfix 947369. Hotfix 947369 resolves issues of noncompliance with RFC 3542.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
947369 Windows Server 2003 does not set the value of the icmp6_cksum field in the icmp6_hdr structure for ICMPv6 packets
Hotfix 950092 and hotfix 947369 together make sure that third-party vendors pass the tests for the IPv6 Ready Logo Phase-2 certification as of April 15, 2008.

For more information about the RFC 4861 specifications that relate to the receipt of Neighbor Advertisements, visit the following Internet Engineering Task Force (IETF) Web site:
http://tools.ietf.org/tools/rfcmarkup/rfcmarkup.cgi?rfc=4861#section-7.2.5

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site:
http://www.microsoft.com/windowsxp/64bit/default.mspx
For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site:
http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx
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

Properties

Article ID: 950092 - Last Review: June 4, 2008 - Revision: 1.1
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows XP Professional x64 Edition
Keywords: 
kbexpertiseinter kbwinserv2003postsp2fix kbautohotfix kbbug kbfix kbhotfixserver kbqfe KB950092

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com