Symptoms

Consider the following scenario:

  • You install the Routing and Remote Access role service on a multi-homed computer that is running Windows Server 2008 R2.

  • You configure the computer as a local area network (LAN) router between two network segments.

  • The Virtual LAN (VLAN) option is enabled in at least one network segment.

  • You send IP packets from one network segment to the other network segment through the LAN router.

In this scenario, the IP packets are not routed to their destination hosts in the other network segment.

Cause

This issue occurs because the TCP/IP driver handles the VLAN identifier in the IP packets incorrectly when the TCP/IP driver forwards these packets from one network segment to the other network segment in a VLAN environment.

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.

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, submit a request to 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=supportNote 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 Server 2008 R2

  • Windows Server 2008 R2 Service Pack 1 (SP1)

Additionally, the Routing and Remote Access role service must be installed.

For more information about how to obtain 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 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.

    Version

    Product

    SR_Level

    Service branch

    6.1.760
    0.
    16xxx

    Windows Server 2008 R2

    RTM

    GDR

    6.1.760
    0.
    20xxx

    Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.
    17xxx

    Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.
    21xxx

    Windows Server 2008 R2

    SP1

    LDR

  • 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" 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 x64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.1.7600.16385

288,336

14-Jul-2009

01:47

x64

Tcpip.sys

6.1.7600.16810

1,896,832

06-May-2011

05:17

x64

Fwpkclnt.sys

6.1.7600.20961

288,128

06-May-2011

05:28

x64

Tcpip.sys

6.1.7600.20961

1,893,248

06-May-2011

05:29

x64

Fwpkclnt.sys

6.1.7601.17514

288,640

20-Nov-2010

13:33

x64

Tcpip.sys

6.1.7601.17621

1,923,968

06-May-2011

05:32

x64

Fwpkclnt.sys

6.1.7601.21722

288,640

06-May-2011

05:23

x64

Tcpip.sys

6.1.7601.21722

1,927,552

06-May-2011

05:23

x64

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 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 Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_47576807058a36142b3aeebd64e34224_31bf3856ad364e35_6.1.7601.17612_none_ad5f86e664eaa849.manifest

File version

Not applicable

File size

706

Date (UTC)

06-May-2011

Time (UTC)

09:37

Platform

Not applicable

File name

Amd64_494e962e5e651f20e241c0fa12fc6623_31bf3856ad364e35_6.1.7601.21722_none_92d275eecf27552f.manifest

File version

Not applicable

File size

706

Date (UTC)

06-May-2011

Time (UTC)

09:37

Platform

Not applicable

File name

Amd64_4c170d7c0b0f0173ba9ed6316e826539_31bf3856ad364e35_6.1.7600.16810_none_170b7411e34f45ac.manifest

File version

Not applicable

File size

706

Date (UTC)

06-May-2011

Time (UTC)

09:37

Platform

Not applicable

File name

Amd64_d8f81e7f71f1c012df73fe8bf3037079_31bf3856ad364e35_6.1.7600.20961_none_f753b37fec8d734d.manifest

File version

Not applicable

File size

706

Date (UTC)

06-May-2011

Time (UTC)

09:37

Platform

Not applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16810_none_0f59bb797fe2f716.manifest

File version

Not applicable

File size

3,784

Date (UTC)

06-May-2011

Time (UTC)

10:02

Platform

Not applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20961_none_0fae48f299283bec.manifest

File version

Not applicable

File size

3,838

Date (UTC)

06-May-2011

Time (UTC)

06:07

Platform

Not applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.17612_none_114219137d0795b0.manifest

File version

Not applicable

File size

3,784

Date (UTC)

06-May-2011

Time (UTC)

10:02

Platform

Not applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21722_none_11c0e5f2962d516b.manifest

File version

Not applicable

File size

3,838

Date (UTC)

06-May-2011

Time (UTC)

07:01

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

3,215

Date (UTC)

06-May-2011

Time (UTC)

09:37

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×