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 2003 does not set the value of the icmp6_cksum field in the icmp6_hdr structure for ICMPv6 packets after you install security update 953230 (MS08-037)


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use the socket function to create an Internet Control Message Protocol for IPv6 (ICMPv6) raw socket on a computer that is running Windows Server 2003.
  • You build an ICMP header and set the value of icmp6_cksum field to 0.
  • You use the sendto API function to send the created package.
  • Security update 953230 that is documented in the security bulletin MS08-037 is installed on the computer.
In this scenario, the value of the icmp6_cksum field in the icmp6_hdr structure keeps the value of 0 in the transmitted packet. This behavior does not comply with the Request for Comment (RFC) 3542 requirements. Additionally, the functions of some applications fail if the following conditions are true:
  • The application uses the ICMPv6 protocol.
  • The application expects that Windows Server 2003 will set the value of the icmp6_cksum field.

↑ Back to the top


Resolution

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, the computer must be running one of the following operating systems:
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows XP Professional x64 Edition
For more information about how to install the Windows Server 2003 service pack, 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 any other 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.
For all supported x86-based versions of Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Tcpip6.sys5.2.3790.4597247,74401-Oct-200915:08Not ApplicableSP2
For all supported x64-based versions of Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Tcpip6.sys5.2.3790.4597394,62401-Oct-200917:25x64SP2Not Applicable
For all supported Itanium-based versions of Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Tcpip6.sys5.2.3790.4597799,36001-Oct-200917:24Not ApplicableSP2Not Applicable
For all supported Windows XP professional x64 Edition

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Tcpip6.sys5.2.3790.4597394,62401-Oct-200917:25x64SP2Not Applicable

↑ 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
For more information about related IPV6 Checksum Issue, 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
For more information about the security update 953230 that is documented in the security bulletin MS08-037, click the following article numbers to view the articles in the Microsoft Knowledge Base:
951746� MS08-037: Description of the security update for DNS in Windows Server 2008, in Windows Server 2003, and in Windows 2000 Server (DNS server-side): July 8, 2008
951748� MS08-037: Description of the security update for DNS in Windows Server 2003, in Windows XP, and in Windows 2000 Server (client side): July 8, 2008
953230� MS08-037: Vulnerabilities in DNS could allow spoofing

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: For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbsurveynew, kbautohotfix, kbexpertiseinter, kbbug, kbfix, KB974927

↑ Back to the top

Article Info
Article ID : 974927
Revision : 2
Created on : 2/18/2010
Published on : 2/18/2010
Exists online : False
Views : 421