Consider the following scenario:
- You have a computer that is running Windows Server 2008 R2 or Windows 7.
- An application or service uses Winsock API or Winsock Kernel API to make network connections on the computer.
In this scenario, the application or service randomly stops responding.
For example, consider the following scenario:
- You install the Remote Desktop Services role on a computer that is running Windows Server 2008 R2.
- You run Citrix XenApp 6 on the computer. The application uses Winsock Kernel API to make network connections.
In this scenario, the XenAPP randomly stops responding when this issue occurs. Additionally, you experience the following symptoms:
- Users cannot make new remote desktop connections to the computer.
- The following event is added to the system event log: Source: Service Control Manager
Date: <date & time>
Event ID: 7011
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <computer name>
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
CAUSE
This issue occurs because of a race condition in the TCP/IP driver (tcpip.sys)….
This issue occurs because of a race condition in the TCP/IP driver (tcpip.sys).
RESOLUTION
Hotfix information A supported hotfix is available from Microsoft. However, this…
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 (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 Server 2008 R2
- Windows Server 2008 R2 Service Pack 1 (SP1)
- Windows 7
- Windows 7 Service Pack 1 (SP1)
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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table: Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760 0. 20xxx
Windows Server 2008 R2 and Windows 7
RTM
LDR
6.0.760 1. 21xxx
Windows Server 2008 R2 and Windows 7
SP1
LDR
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that ar…
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 Winsock Kernel, visit the following Microsoft Develop…
For more information about Winsock Kernel, visit the following Microsoft Developer Network (MSDN) website:
General information about Winsock Kernel (http://msdn.microsoft.com/en-us/library/ff571084(v=VS.85).aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
- Windows Server 2008 R2 Enterprise
- Wi
ndows Server 2008 R2 Datacenter - Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Web Server 2008 R2
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
<