Article ID: 156319 - Last Review: July 11, 2005 - Revision: 1.2

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

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q156319
Expand all | Collapse all

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.
Back to the top

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.
Back to the top

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.
Back to the top

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  (http://support.microsoft.com/kb/150523/EN-US/ ) BUG: Socket Inheritance in Windows 95 and Windows NT 3.51
Back to the top
APPLIES TO
  • Microsoft Platform Software Development Kit-January 2000 Edition, when used with:
    • Microsoft Windows 95
    • Microsoft Windows 98 Standard Edition
Back to the top
Keywords: 
kbbug kbwinsock kbapi kbnetwork KB156319
Back to the top