Article ID: 884843
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Service Pack 4
SYMPTOMS
Assume the following scenario: A Winsock program is running on your Microsoft Windows 2000 Server-based computer with Service Pack 4 (SP4) applied. Additionally, the hotfix that is described in the following Microsoft Knowledge Base article is installed on your computer:
839045 Socket applications quit with a WSAEWOULDBLOCK error in Windows 2000 Server
The socket program creates a socket and then uses the WSAEventSelect function to select the FD_READ event. The socket program also uses the WSAWaitForMultipleEvent function to wait for data on the listening socket.
In this scenario, you may notice the following symptoms:
- The socket program on the client computer does not return the FD_READ network event notification on the connected socket for the WSAEnumNetworkEvents function call.
- The WSAWaitForMultipleEvent function call is not returned when data arrives. Therefore, the function call times out.
- The socket program does not read data, even though the client computer is still connected to the listening socket.
- The socket program does not read data, even though there is data available to read from the socket.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
This hotfix requires Windows 2000 Server SP4.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces the hotfix from Knowledge Base article 839045.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------- 08-Jan-2005 17:58 5.0.2195.7019 119,248 Afd.sys 19-Jun-2003 20:05 5.0.2195.6602 108,816 Msafd.dll 19-Jun-2003 20:05 5.0.2195.6706 332,144 Tcpip.sys 19-Jun-2003 20:05 5.0.2195.6655 16,240 Tdi.sys 19-Jun-2003 20:05 5.0.2195.6601 17,680 Wshtcpip.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For additional information about the standard terminology that is used to describe Microsoft software updates, 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
Keywords: kbbug kbfix kbwin2000presp5fix kbhotfixserver kbqfe KB884843
