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.

IP addresses that are used for reconnection are not listed completely in the RD Connection Broker setting in Windows Server 2008 R2 or in Windows 7


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a client computer that is running Windows Server 2008 R2 or Windows 7.
  • You use the Remote Desktop Session Host Configuration snap-in to connect to a multi-homed Windows Server 2008 R2-based computer.
  • You configure some RDP-TCP connections to use specific network adapters.
  • You edit the RD Connection Broker setting.
  • On the RD Connection Broker tab, you try to select the check box next to each IP address that you want to use in the Select IP addresses to be used for reconnection box.
In these scenarios, the IP address list may be empty or incomplete. Therefore, you cannot select the correct IP addresses for reconnection. Because of this issue, remote desktop service clients may be unable to reconnect after their sessions are disconnected.

↑ Back to the top


Cause

This issue occurs because the used IP filtering logic is incorrect when multiple RDP listeners are configured to use different IP addresses in the RD Connection Broker setting.

↑ Back to the top


Resolution

To resolve this issue, install the following hotfix on both the Windows 7 or Windows Server 2008 R2-based client computer and the multi-homed Windows Server 2008 R2-based computer.

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 exist, 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: 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 with Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 with Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 service pack 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 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 to which each hotfix applies.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.20xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical 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 7
File nameFile versionFile sizeDateTimePlatform
Tscfgwmi.dll6.1.7600.20971153,08823-May-201104:37x86
Tscfgwmi.dll6.1.7601.21732153,60023-May-201106:09x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Tscfgwmi.dll6.1.7600.20971198,14423-May-201105:24x64
Tscfgwmi.dll6.1.7601.21732199,16823-May-201105:08x64
Sdclient.dll6.1.7600.20971231,93623-May-201105:23x64
Tssdjet.dll6.1.7600.2097195,74423-May-201105:24x64
Sdclient.dll6.1.7601.17514231,93620-Nov-201013:27x64
Tssdjet.dll6.1.7601.2173295,74423-May-201105:08x64
Tscfgwmi.dll6.1.7600.20971153,08823-May-201104:37x86
Tscfgwmi.dll6.1.7601.21732153,60023-May-201106:09x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Tscfgwmi.dll6.1.7600.20971450,56023-May-201104:04IA-64
Tscfgwmi.dll6.1.7601.21732452,60823-May-201104:06IA-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_8d1c2c2ac9f99c70b244f2f23113b5b4_31bf3856ad364e35_6.1.7600.20971_none_5ffb6059e2cb1315.manifest
File versionNot applicable
File size716
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameX86_a42bb3ea098872c0ddf3838ba94e043b_31bf3856ad364e35_6.1.7601.21732_none_155bc45491ad52b6.manifest
File versionNot applicable
File size716
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameX86_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7600.20971_none_eb985d45f96dec30.manifest
File versionNot applicable
File size16,996
Date (UTC)23-May-2011
Time (UTC)05:03
PlatformNot applicable
File nameX86_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7601.21732_none_edaafa45f67301af.manifest
File versionNot applicable
File size16,996
Date (UTC)23-May-2011
Time (UTC)06:32
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_32a1d61525b823ea04ec3519a7a8199f_31bf3856ad364e35_6.1.7600.20971_none_ca1f01cfb2783c75.manifest
File versionNot applicable
File size720
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameAmd64_4e178c1754af66bd384a2bbbe79f9079_31bf3856ad364e35_6.1.7601.21732_none_b6ead19585d9ebd9.manifest
File versionNot applicable
File size732
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameAmd64_78c9dca6571e27250c4accb9eca0a8c5_31bf3856ad364e35_6.1.7601.21732_none_108c44715ea1c5f3.manifest
File versionNot applicable
File size720
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameAmd64_8d1c2c2ac9f99c70b244f2f23113b5b4_31bf3856ad364e35_6.1.7600.20971_none_bc19fbdd9b28844b.manifest
File versionNot applicable
File size718
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameAmd64_a42bb3ea098872c0ddf3838ba94e043b_31bf3856ad364e35_6.1.7601.21732_none_717a5fd84a0ac3ec.manifest
File versionNot applicable
File size718
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameAmd64_dba1304f183f0ce81feb17656d53b262_31bf3856ad364e35_6.1.7600.20971_none_787d51df50b0681a.manifest
File versionNot applicable
File size732
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameAmd64_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7600.20971_none_47b6f8c9b1cb5d66.manifest
File versionNot applicable
File size17,000
Date (UTC)23-May-2011
Time (UTC)05:54
PlatformNot applicable
File nameAmd64_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7601.21732_none_49c995c9aed072e5.manifest
File versionNot applicable
File size17,000
Date (UTC)23-May-2011
Time (UTC)07:14
PlatformNot applicable
File nameAmd64_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.1.7600.20971_none_5fea081babf13345.manifest
File versionNot applicable
File size39,088
Date (UTC)23-May-2011
Time (UTC)05:57
PlatformNot applicable
File nameAmd64_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.1.7601.21732_none_61fca51ba8f648c4.manifest
File versionNot applicable
File size40,864
Date (UTC)23-May-2011
Time (UTC)18:30
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size4,463
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameX86_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7600.20971_none_eb985d45f96dec30.manifest
File versionNot applicable
File size16,996
Date (UTC)23-May-2011
Time (UTC)05:03
PlatformNot applicable
File nameX86_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7601.21732_none_edaafa45f67301af.manifest
File versionNot applicable
File size16,996
Date (UTC)23-May-2011
Time (UTC)06:32
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_7d2e71079604924a4ca40a7a391fba32_31bf3856ad364e35_6.1.7601.21732_none_76b6d6ec631a48a1.manifest
File versionNot applicable
File size718
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameIa64_b4331bf6252a01da89dd4afadd1279ab_31bf3856ad364e35_6.1.7600.20971_none_458ef127ec4e3de4.manifest
File versionNot applicable
File size718
Date (UTC)23-May-2011
Time (UTC)18:26
PlatformNot applicable
File nameIa64_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7600.20971_none_eb9a013bf96bf52c.manifest
File versionNot applicable
File size16,998
Date (UTC)23-May-2011
Time (UTC)05:54
PlatformNot applicable
File nameIa64_microsoft-windows-t..ervices-wmiprovider_31bf3856ad364e35_6.1.7601.21732_none_edac9e3bf6710aab.manifest
File versionNot applicable
File size16,998
Date (UTC)23-May-2011
Time (UTC)07:15
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2536840
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 196