Microsoft KB Archive/186416

From BetaArchive Wiki
Knowledge Base


System Hang Results from Large Number of Notify Syncs

Article ID: 186416

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT 4.0 Service Pack 3



This article was previously published under Q186416

SYMPTOMS

Your computer running Windows NT 4.0 Service Pack 3 (SP3) that is configured as a domain controller may stop responding (hang) when approximately 400 users with a centralized desktop scheme are connected to the domain controller.

CAUSE

With this centralized desktop scheme, the most significant network load came about when the Start Menu and Desktop were refreshed. The Explorer shell from the client causes a series of NotifyChangeDirectoryFile calls to be made to the file system of the server during these refresh cycles. Each call causes a notify sync object to be allocated and places an IRP in the notify queue.

In this configuration, the 400 users generated a significant number of notify syncs, which eventually would create a mismatch between an associated IRP and its notify synch object because of a timing issue.

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 the Microsoft 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.

Keywords: kbhotfixserver kbqfe kbbug kbfix KB186416