IGMP v1 membership report packets are sent to incorrect destinations on a computer that is running Windows Server 2008, Windows Vista, Windows 7 or Windows Server 2008 R2

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

On This Page

SYMPTOMS

A computer that is running Windows Server 2008, Windows Vista, Windows 7 or Windows Server 2008 R2 sends Internet Group Management Protocol (IGMP) v1 membership report packets to the incorrect destinations. Therefore, applications or services that use the Internet Group Management Protocol (IGMP) v1 protocol are dropped by the router from the multicast group and do not receive any more traffic.

In a captured network trace, the destination IPv4 address differs from the multicast address in the IGMP v1 membership report. Therefore, the design does not comply with Request for Comments (RFC) 1112.

For example, the following resembles a captured network trace that is generated when this issue occurs.

Frame: Number = 33, Captured Frame Length = 46, MediaType = ETHERNET
+ Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[MAC address],SourceAddress:[MAC address]
+ Ipv4: Src = IP address, Dest = IP address, Next Protocol = IGMP, Packet ID = 5009, Total IP Length = 32
- Igmp: IGMPv1 membership report
Type: IGMPv1 membership report, 18(0x12)
- Igmpv1:
Unused: 0 (0x0)
CheckSum: 13509 (0x34C5)
MulticastAddress: IP address

CAUSE

This issue occurs when multiple IGMP v1 membership reports time out at the same time. In this situation, the TCP/IP driver (Tcpip.sys) does not handle file destination IP addresses for each IGMP v1 membership report packet correctly.

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 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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or 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 in this package, you do not have to make any changes to 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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.0.6002.2254231,23207-Dec-201014:42x86
Tcpip.sys6.0.6002.22542912,78408-Dec-201010:43x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.0.6002.2254240,44807-Dec-201015:13x64
Tcpip.sys6.0.6002.225421,423,76008-Dec-201010:40x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.0.6002.2254280,89607-Dec-201015:16IA-64
Tcpip.sys6.0.6002.225422,967,95208-Dec-201010:34IA-64
Windows 7 and 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 0 . 20xxxWindows 7 and Windows Server 2008 R2RTMLDR
    6.1.760 1 . 21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and 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 x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20916187,26405-Mar-201105:56x86
Tcpip.sys6.1.7600.209161,298,30405-Mar-201105:57x86
Fwpkclnt.sys6.1.7601.21675187,77605-Mar-201105:29x86
Tcpip.sys6.1.7601.216751,299,32805-Mar-201105:29x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20916288,12805-Mar-201106:30x64
Tcpip.sys6.1.7600.209161,893,24805-Mar-201106:30x64
Fwpkclnt.sys6.1.7601.21675288,64005-Mar-201106:20x64
Tcpip.sys6.1.7601.216751,927,55205-Mar-201106:20x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20916482,68805-Mar-201105:25IA-64
Tcpip.sys6.1.7600.209163,801,47205-Mar-201105:26IA-64
Fwpkclnt.sys6.1.7601.21675483,20005-Mar-201105:16IA-64
Tcpip.sys6.1.7601.216753,803,00805-Mar-201105:17IA-64

WORKAROUND

To work around this issue, use the IGMP v2 protocol.

STATUS

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

MORE INFORMATION

For more information about Request for Comments (RFC) 1112, visit the following Internet FAQ archives website:
Request for Comments (RFC) 1112
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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameX86_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22542_none_886412e81bcf7dfd.manifest
File versionNot applicable
File size4,845
Date (UTC)07-Dec-2010
Time (UTC)16:57
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22542_none_b564ef337cc8c467.manifest
File versionNot applicable
File size6,762
Date (UTC)08-Dec-2010
Time (UTC)10:46
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22542_none_e482ae6bd42cef33.manifest
File versionNot applicable
File size5,122
Date (UTC)07-Dec-2010
Time (UTC)17:18
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22542_none_11838ab73526359d.manifest
File versionNot applicable
File size6,784
Date (UTC)08-Dec-2010
Time (UTC)10:46
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22542_none_8865b6de1bcd86f9.manifest
File versionNot applicable
File size5,118
Date (UTC)07-Dec-2010
Time (UTC)17:08
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22542_none_b56693297cc6cd63.manifest
File versionNot applicable
File size6,773
Date (UTC)08-Dec-2010
Time (UTC)10:46
PlatformNot applicable

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot Applicable
File size2,773
Date (UTC)07-Mar-2011
Time (UTC)13:09
PlatformNot Applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20916_none_b3cabe7ce09dbdb4.manifest
File versionNot Applicable
File size3,834
Date (UTC)05-Mar-2011
Time (UTC)06:16
PlatformNot Applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21675_none_b56f39caddf5bac8.manifest
File versionNot Applicable
File size3,834
Date (UTC)05-Mar-2011
Time (UTC)05:56
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20916_none_0fe95a0098fb2eea.manifest
File versionNot Applicable
File size3,838
Date (UTC)05-Mar-2011
Time (UTC)07:23
PlatformNot Applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21675_none_118dd54e96532bfe.manifest
File versionNot Applicable
File size3,838
Date (UTC)05-Mar-2011
Time (UTC)06:49
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size3,215
Date (UTC)07-Mar-2011
Time (UTC)13:09
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20916_none_b3cc6272e09bc6b0.manifest
File versionNot Applicable
File size3,836
Date (UTC)05-Mar-2011
Time (UTC)07:16
PlatformNot Applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21675_none_b570ddc0ddf3c3c4.manifest
File versionNot Applicable
File size3,836
Date (UTC)05-Mar-2011
Time (UTC)06:44
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,168
Date (UTC)07-Mar-2011
Time (UTC)13:09
PlatformNot Applicable

Properties

Article ID: 2470853 - Last Review: April 22, 2011 - Revision: 5.0
APPLIES TO
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Foundation
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Home Basic
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Home Premium
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Starter
  • Windows Vista Ultimate
  • Windows Vista Ultimate 64-bit Edition
  • Windows 7 Enterprise
  • Windows 7 Home Basic
  • Windows 7 Home Premium
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Foundation
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2470853

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