Article ID: 289152 - View products that this article applies to.
This article was previously published under Q289152
This article has been archived. It is offered "as is" and will no longer be updated.
If a program starts multiple child processes that have duplicated a socket, and the processes try to use the duplicate at the same time, both the processes and the program stop responding.
To 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:
(https://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Microsoft 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 2.
This behavior can occur, for example, when process A calls WSADuplicateSocket() and then passes the resulting structure to process B by using an interprocess communication. If process B is currently creating a duplicate socket by means of a call to WSPSocket(), a second call to WSPSocket() before the first is complete may stop both the socket duplication code and the program.
Article ID: 289152 - Last Review: October 23, 2013 - Revision: 3.2