Sockets-based Child Processes Are Not Stopped

This article was previously published under Q192266
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
Sockets-based child processes are not stopped and appear as "zombieprocesses."
CAUSE
There is a timing window where the TCP connection is not closed correctlyon the Windows NT side and data that has not been acknowledged yet isdiscarded.
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 theMicrosoft 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.
MORE INFORMATION

Zombie processes are child processes that are no longer running, but thekernel still needs to keep information about them. In this case, theseprocesses are waiting for an event that never comes.
Properties

Article ID: 192266 - Last Review: 10/10/2013 20:51:38 - Revision: 1.3

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB192266
Feedback