Knowledge Base

BUG: Inherited Socket Becomes Invalid if Parent Exits on Windows 95 and Windows 98

Article ID: 156319

Article Last Modified on 7/11/2005

APPLIES TO

This article was previously published under Q156319

SYMPTOMS

If a child process is using a socket inherited from its parent, the socket will become unusable when the parent process exits. Winsock APIs such as send() fail with WSAENOTSOCK.

WORKAROUND

To avoid this problem, you must ensure that the parent process is active as long as the socket is needed by the child processes.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For more information on how to inherit sockets in child processes on Windows 95, please see the following article in the Microsoft Knowledge Base.

150523 BUG: Socket Inheritance in Windows 95 and Windows NT 3.51

Keywords: kbbug kbwinsock kbapi kbnetwork KB156319


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.