Symptoms

Consider the following scenario:

  • You have a computer that is running Windows 7 or Windows Server 2008 R2.

  • An application or a service calls the closesocket function to close a socket on the computer.

In this scenario, the application or the service stops responding. You have to restart the application or the service to recover from this issue.

Notes

  • Sometimes the computer does not respond to the Ping command or to any remote command when this issue occurs. In this case, you receive the following error message when you try to use a Server Message Block (SMB) connection to connect to the problematic server:

    No logon server available

  • This issue is fixed in Windows Server 2008 R2 Service Pack 1 (SP1) and in Windows 7 SP1.

Cause

This issue occurs because of a timing issue that involves "neighbor reachability."

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=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 7

  • 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 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.
    20xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    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 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 name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.1.7600.20924

187,264

15-Mar-2011

05:22

x86

Tcpip.sys

6.1.7600.20924

1,298,304

15-Mar-2011

05:22

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.1.7600.20924

288,128

15-Mar-2011

05:56

x64

Tcpip.sys

6.1.7600.20924

1,893,248

15-Mar-2011

05:56

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.1.7600.20924

482,688

15-Mar-2011

04:37

IA-64

Tcpip.sys

6.1.7600.20924

3,800,960

15-Mar-2011

04:37

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 closesocket function, visit the following Microsoft developer network (MSDN) website:

General information about the closesocket functionFor 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 name

Update.mum

File version

Not applicable

File size

1,880

Date (UTC)

15-Mar-2011

Time (UTC)

08:41

Platform

Not applicable

File name

X86_9dd47e6cc32940e3a12be5f20f04261e_31bf3856ad364e35_6.1.7600.20924_none_7077ddfd38f73e61.manifest

File version

Not applicable

File size

702

Date (UTC)

15-Mar-2011

Time (UTC)

08:41

Platform

Not applicable

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20924_none_b3bdedfce0a7a6f7.manifest

File version

Not applicable

File size

3,834

Date (UTC)

15-Mar-2011

Time (UTC)

05:45

Platform

Not applicable

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

File name

Amd64_3b3c33e0ba931a44963e231b53d1f024_31bf3856ad364e35_6.1.7600.20924_none_ddc2e27287236409.manifest

File version

Not applicable

File size

706

Date (UTC)

15-Mar-2011

Time (UTC)

08:41

Platform

Not applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20924_none_0fdc89809905182d.manifest

File version

Not applicable

File size

3,838

Date (UTC)

15-Mar-2011

Time (UTC)

06:51

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,114

Date (UTC)

15-Mar-2011

Time (UTC)

08:41

Platform

Not applicable

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

File name

Ia64_8f08226acd4bc2d2d8c1c276f18f8c6a_31bf3856ad364e35_6.1.7600.20924_none_f3b406eca6cefc7c.manifest

File version

Not applicable

File size

704

Date (UTC)

15-Mar-2011

Time (UTC)

08:41

Platform

Not applicable

File name

Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20924_none_b3bf91f2e0a5aff3.manifest

File version

Not applicable

File size

3,836

Date (UTC)

15-Mar-2011

Time (UTC)

06:45

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,690

Date (UTC)

15-Mar-2011

Time (UTC)

08:41

Platform

Not applicable

Author: mohak;stevenxu
Writer: v-liangc
Tech Reviewer: mohak;stevenxu;hangwu;amanjain
Editor: v-doskir

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!

×