Microsoft KB Archive/185727

= BUG: closesocket Fails with 10038 After _open_osfhandle =

Article ID: 185727

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT 4.0 Service Pack 3
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q185727



SYMPTOMS
The _open_osfhandle function allocates a C run-time file handle and sets it to point to the operating-system file handle. When _open_osfhandle function is used on a socket descriptor, both _close and closesocket should be called before exiting. However, on Windows NT 4.0 Service Pack 3, closesocket after _close returns 10038.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack



STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

This bug is not present in Windows NT 4.0 Service Pack 1, Service Pack 2, or the original build of Windows NT 4.0.



MORE INFORMATION
When _open_osfhandle is used on a socket descriptor, both _close and closesocket should be called before exiting. _close only closes the file handle. closesocket has to be called as well to close the socket descriptor and clean up the underlying socket object.

Keywords: kbbug kbfix kbwinsock kbapi kbnetwork KB185727

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.