Microsoft KB Archive Search

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.

  1. Home
  2. Applications or services cannot update their routing tables after they receive route change notifications in Windows Server 2008 R2 or in Windows 7

Applications or services cannot update their routing tables after they receive route change notifications in Windows Server 2008 R2 or in Windows 7

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You configure multiple addresses for a network adapter on a computer that is running Windows Server 2008 R2 or Windows 7.
  • You change IP address information about the network adapter. The changed IP address is not the first bound address. For example, you add a new IP address to the adapter, you remove an IP address, or you change the IP address configuration.

    Note This operation should trigger the operating system to send route change notifications.
  • You run an application or a service that registers to receive route change notifications on the computer.
In this scenario, the application or service cannot update the routing table after the route change notification is received.

Note The routing table is maintained by the application or the service. It is not the system routing table.

Here is a sample scenario:
  • You install Routing and Remote Access Service (RRAS) on a computer that is running Windows Server 2008 R2. This service registers to receive route change notifications.
  • You add a second IP address to a network adapter on the computer.
  • You open the Routing and Remote Access window, right-click the network adapter, and then select Show IP Routing Table.
In this scenario, the displayed routing table does not show the newly added IP address. The expected behavior is that the RRAS updates the routing table after the service receives route change notifications.

↑ Back to the top

Cause

This issue occurs because the "next-hop" address information in the route change notification is incorrect.

↑ Back to the top

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 that is 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 website:
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 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

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 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 to 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.
    VersionProductSR_LevelService branch
    6.1.760
    0.20xxx    		Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.17xxx    		Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx    		Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, very important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20861187,26418-Dec-201005:35x86
Tcpip.sys6.1.7600.208611,298,30418-Dec-201005:35x86
Fwpkclnt.sys6.1.7601.17514187,77620-Nov-201012:29x86
Tcpip.sys6.1.7601.216241,290,11218-Dec-201008:05x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20861288,12818-Dec-201006:12x64
Tcpip.sys6.1.7600.208611,893,24818-Dec-201006:13x64
Fwpkclnt.sys6.1.7601.17514288,64020-Nov-201013:33x64
Tcpip.sys6.1.7601.216241,923,96818-Dec-201008:56x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20861482,68818-Dec-201005:23IA-64
Tcpip.sys6.1.7600.208613,801,47218-Dec-201005:23IA-64
Fwpkclnt.sys6.1.7601.17514483,20020-Nov-201010:33IA-64
Tcpip.sys6.1.7601.216243,779,45618-Dec-201009:41IA-64

↑ 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

Additional file information

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

Additional files for all supported x86-based versions of Windows 7
File nameX86_48a52f5e57bb53a81aa1b4df3e72d38f_31bf3856ad364e35_6.1.7600.20861_none_98803cf45f49492f.manifest
File versionNot applicable
File size702
Date (UTC)20-Dec-2010
Time (UTC)21:42
PlatformNot applicable
File nameX86_b28c73881d5ac0ffeae1b2bccacf67a0_31bf3856ad364e35_6.1.7601.21624_none_2d63e4f877ecc0e0.manifest
File versionNot applicable
File size702
Date (UTC)20-Dec-2010
Time (UTC)21:42
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20861_none_b38fab88e0cacd8f.manifest
File versionNot applicable
File size3,834
Date (UTC)18-Dec-2010
Time (UTC)06:00
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21624_none_b5a4491cddce15bc.manifest
File versionNot applicable
File size3,780
Date (UTC)20-Dec-2010
Time (UTC)21:46
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_ac5bbd960f9ab414c6d6f46a68cfc403_31bf3856ad364e35_6.1.7601.21624_none_dced42728da54511.manifest
File versionNot applicable
File size706
Date (UTC)20-Dec-2010
Time (UTC)21:42
PlatformNot applicable
File nameAmd64_bd3ec78830fec655267951f994208d5a_31bf3856ad364e35_6.1.7600.20861_none_f7230879db68c351.manifest
File versionNot applicable
File size706
Date (UTC)20-Dec-2010
Time (UTC)21:42
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20861_none_0fae470c99283ec5.manifest
File versionNot applicable
File size3,838
Date (UTC)18-Dec-2010
Time (UTC)06:57
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21624_none_11c2e4a0962b86f2.manifest
File versionNot applicable
File size3,784
Date (UTC)20-Dec-2010
Time (UTC)21:49
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_30ae1a7718518a8442509f3ca00df76a_31bf3856ad364e35_6.1.7601.21624_none_1ae9facae6fbc5eb.manifest
File versionNot applicable
File size704
Date (UTC)20-Dec-2010
Time (UTC)21:42
PlatformNot applicable
File nameIa64_d6d4ce44139fed7e943389ce31852b39_31bf3856ad364e35_6.1.7600.20861_none_58800dbdbf769391.manifest
File versionNot applicable
File size704
Date (UTC)20-Dec-2010
Time (UTC)21:42
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20861_none_b3914f7ee0c8d68b.manifest
File versionNot applicable
File size3,836
Date (UTC)18-Dec-2010
Time (UTC)06:54
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21624_none_b5a5ed12ddcc1eb8.manifest
File versionNot applicable
File size3,782
Date (UTC)20-Dec-2010
Time (UTC)21:43
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2465408
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 328