Sockets-based Child Processes Are Not Stopped

View products that this article applies to.

This article was previously published under Q192266

Expand all | Collapse all

SYMPTOMS

Sockets-based child processes are not stopped and appear as "zombie processes."

Back to the top

CAUSE

There is a timing window where the TCP connection is not closed correctly on the Windows NT side and data that has not been acknowledged yet is discarded.

Back to the top

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 the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

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.

Back to the top

MORE INFORMATION

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

Back to the top