Program May Hang When It Calls the ioctlsocket() Function (297110)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Professional SP1
This article was previously published under Q297110 SYMPTOMS
If you have a socket based client/server program in which the client and server are running on two different physical computer, and if the client programs uses the ioctlsocket function to make a socket non-blocking, the client program may stop responding (hang). When this problem occurs, the only way to recover is to "kill" the client program.
CAUSE
This problem occurs because the Windows 2000 Socket services are not handling the socket non-blocking request correctly.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
----------------------------------------------------------
4/16/2001 04:40p 5.0.2195.3503 118,800 Afd.sys
5/2/2001 07:53p 5.0.2195.3566 104,720 Msafd.dll
5/2/2001 06:07p 5.0.2195.3560 311,696 Tcpip.sys
4/6/2001 05:55p 5.0.2195.3474 16,208 Tdi.sys
5/2/2001 07:53p 5.0.2195.2104 17,680 Wshtcpip.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB297110 |
---|
|