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.

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

  • The virtual LAN (VLAN) option is enabled in only one network segment.

  • An untagged side of the two VLAN network segments consists of a pure LAN connection or an Internet Protocol security (IPsec) site-to-site tunnel.

  • You send IP packets from the tagged VLAN network segment to the untagged VLAN network segment through the LAN router.

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

Cause

This issue occurs because the VLAN tag is not removed from the IP packets that are forwarded from the tagged VLAN network segment to the untagged side or an IPsec site-to-site tunnel.

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, go to the following Microsoft website:

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 Windows Server 2008 Service Pack 2 (SP2). Additionally, you must have the Routing and Remote Access role service installed.

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:

968849How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, 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 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.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Server 2008

    SP2

    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" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important for 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.

File name

File version

File size

Date

Time

Platform

Tcpipreg.sys

6.0.6002.22949

31,232

12-Oct-2012

14:21

x86

Tcpip.sys

6.0.6002.22949

913,792

13-Oct-2012

06:21

x86


File name

File version

File size

Date

Time

Platform

Tcpipreg.sys

6.0.6002.22949

40,448

12-Oct-2012

15:01

x64

Tcpip.sys

6.0.6002.22949

1,418,624

13-Oct-2012

06:18

x64


File name

File version

File size

Date

Time

Platform

Tcpipreg.sys

6.0.6002.22949

80,896

12-Oct-2012

14:03

IA-64

Tcpip.sys

6.0.6002.22949

2,970,496

13-Oct-2012

06:09

IA-64



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 the IP packets issue, click the following article number to view the article in the Microsoft Knowledge Base:

2661010 IP packets are not routed through a Windows Server 2008 R2–based LAN router in a VLAN environment For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

File name

X86_8d440572ba61f66ea754fcf66aa453c5_31bf3856ad364e35_6.0.6002.22949_none_73283c67f70990fc.manifest

File version

Not applicable

File size

702

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable

File name

X86_9e38e432446c611e31a688944080df94_31bf3856ad364e35_6.0.6002.22949_none_b74767e566e9f0e1.manifest

File version

Not applicable

File size

717

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable

File name

X86_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22949_none_886b1c861bc923fa.manifest

File version

Not applicable

File size

4,845

Date (UTC)

12-Oct-2012

Time (UTC)

19:10

Platform

Not applicable

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22949_none_b56bf8d17cc26a64.manifest

File version

Not applicable

File size

6,762

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable


File name

Amd64_0dedba2af8e0ba122861e127ab9bb3fc_31bf3856ad364e35_6.0.6002.22949_none_9c123beb8c74e371.manifest

File version

Not applicable

File size

706

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable

File name

Amd64_3883e3d0a39190553314438e594e3f6c_31bf3856ad364e35_6.0.6002.22949_none_523e6d93c75f374a.manifest

File version

Not applicable

File size

721

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable

File name

Amd64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22949_none_e489b809d4269530.manifest

File version

Not applicable

File size

5,122

Date (UTC)

12-Oct-2012

Time (UTC)

19:26

Platform

Not applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22949_none_118a9455351fdb9a.manifest

File version

Not applicable

File size

6,784

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable


File name

Ia64_6b861cf5c089398263de43b97c917792_31bf3856ad364e35_6.0.6002.22949_none_f4eb8a262c61e183.manifest

File version

Not applicable

File size

1,066

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

Platform

Not applicable

File name

Ia64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22949_none_886cc07c1bc72cf6.manifest

File version

Not applicable

File size

5,118

Date (UTC)

12-Oct-2012

Time (UTC)

16:58

Platform

Not applicable

File name

Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22949_none_b56d9cc77cc07360.manifest

File version

Not applicable

File size

6,773

Date (UTC)

13-Oct-2012

Time (UTC)

06:25

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?

Any additional feedback? (Optional)

Thank you for your feedback!

×