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. Cannot reuse Wildcard TCP ports on multiple IP addresses in Windows 7 SP1 or Windows Server 2008 R2 SP1

Cannot reuse Wildcard TCP ports on multiple IP addresses in Windows 7 SP1 or Windows Server 2008 R2 SP1

View products that this article applies to.

Symptoms

Assume that you use wildcard TCP ports on multiple IP addresses on the same network adapter in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. In this situation, you cannot reuse the wildcard TCP ports even though the SO_PORT_SCALABILITY socket option that is used to maximize wildcard port allocation is set on all sockets.

For example, when you enable the port scalability feature for remote procedure call (RPC) proxies on a computer, the RPC ports cannot be reused on multiple IP addresses on the same network adapter.

Note The SO_PORT_SCALABILITY socket option enables local port scalability for a socket. That is, port allocation can be maximized by allocating wildcard ports multiple times for different local address port pairs on a local computer.  

↑ Back to the top

Cause

This issue occurs because the scanning operation that looks for addresses to use concludes without actually performing a search.

↑ 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 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 Windows 7 SP1 or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to go to 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 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 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, 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
    1.22xxx    		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
Netio.sys6.1.7601.22277240,47211-Mar-201313:10x86
Fwpkclnt.sys6.1.7601.22277187,73611-Mar-201313:10x86
Tcpip.sys6.1.7601.222771,308,50411-Mar-201313:10x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Netio.sys6.1.7601.22277376,66411-Mar-201313:55x64
Fwpkclnt.sys6.1.7601.22277288,10411-Mar-201313:55x64
Tcpip.sys6.1.7601.222771,901,40011-Mar-201313:55x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Netio.sys6.1.7601.22277711,01611-Mar-201313:00IA-64
Fwpkclnt.sys6.1.7601.22277482,13611-Mar-201312:59IA-64
Tcpip.sys6.1.7601.222773,821,91211-Mar-201313:00IA-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 go to 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_546639867bfc6bb65372cdcf905aaa50_31bf3856ad364e35_6.1.7601.22277_none_cf218a58c095b118.manifest
File versionNot applicable
File size1,054
Date (UTC)11-Mar-2013
Time (UTC)19:25
PlatformNot applicable
File nameX86_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22277_none_58ee76822cdb58e4.manifest
File versionNot applicable
File size2,540
Date (UTC)11-Mar-2013
Time (UTC)13:38
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22277_none_b5711bfeddf4127b.manifest
File versionNot applicable
File size3,834
Date (UTC)11-Mar-2013
Time (UTC)13:39
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_961ef1ee2bd38784a8de64a3408bf8f3_31bf3856ad364e35_6.1.7601.22277_none_903537b50cfe0c95.manifest
File versionNot applicable
File size1,414
Date (UTC)11-Mar-2013
Time (UTC)19:25
PlatformNot applicable
File nameAmd64_a496795964f709e41091e5a2b18fe323_31bf3856ad364e35_6.1.7601.22277_none_61557a7197068ad1.manifest
File versionNot applicable
File size1,060
Date (UTC)11-Mar-2013
Time (UTC)19:25
PlatformNot applicable
File nameAmd64_ea3cee86fad19d4f64c70be9efc81950_31bf3856ad364e35_6.1.7601.22277_none_5711fc7014cb73de.manifest
File versionNot applicable
File size712
Date (UTC)11-Mar-2013
Time (UTC)19:25
PlatformNot applicable
File nameAmd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22277_none_b50d1205e538ca1a.manifest
File versionNot applicable
File size2,542
Date (UTC)11-Mar-2013
Time (UTC)15:12
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22277_none_118fb782965183b1.manifest
File versionNot applicable
File size3,838
Date (UTC)11-Mar-2013
Time (UTC)15:15
PlatformNot applicable
File nameWow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22277_none_bf61bc5819998c15.manifest
File versionNot applicable
File size1,166
Date (UTC)11-Mar-2013
Time (UTC)13:19
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_b54891d0731a0cd5843397f78c6eacf5_31bf3856ad364e35_6.1.7601.22277_none_847bde222ca9a6fb.manifest
File versionNot applicable
File size1,411
Date (UTC)11-Mar-2013
Time (UTC)19:25
PlatformNot applicable
File nameIa64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22277_none_58f01a782cd961e0.manifest
File versionNot applicable
File size2,541
Date (UTC)11-Mar-2013
Time (UTC)13:23
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22277_none_b572bff4ddf21b77.manifest
File versionNot applicable
File size3,836
Date (UTC)11-Mar-2013
Time (UTC)13:25
PlatformNot applicable
File nameWow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22277_none_bf61bc5819998c15.manifest
File versionNot applicable
File size1,166
Date (UTC)11-Mar-2013
Time (UTC)13:19
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2826167
Revision : 1
Created on : 1/7/2017
Published on : 5/14/2013
Exists online : False
Views : 171