BUG: Inherited Socket Becomes Invalid if Parent Exits on Win95

Last reviewed: January 11, 1997
Article ID: Q156319

The information in this article applies to:

Microsoft Win32 Software Development Kit (SDK) for Windows 95, versions 3.51, 4.0

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.

   ARTICLE_ID: Q150523
   TITLE     : BUG: Socket Inheritance in Windows 95 and Windows NT 3.51

KBCategory: kbnetwork kbbuglist
KBSubcategory: kbnocat
Additional reference words: 3.51 4.00 kbdsi

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.