Deadlock in Redirector Delays Opening a File on the Network (268817)


The information in this article applies to:

  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server 4.0
This article was previously published under Q268817

SYMPTOMS

You may occasionally experience delays of about 45 seconds when you access files on a remote server. There are no other performance problems on the network or on the server in general.

CAUSE

There is a deadlock situation when a client workstation posts a large number of directory change notification requests. This deadlock is resolved after 45 seconds. These requests may be issued by:
  • Redirecting user shell folders
  • Open Windows Explorer windows with the focus on a network drive
  • Programs with open documents on a network drive
  • Any code that uses the FindFirstChangeNotification function
The deadlock may occur when more than 48 of these notifications are pending.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later: 
   Date        Time    Size      File name   Platform
   --------------------------------------------------
   11/7/2000   02:46   265,904   Rdr.sys     Intel
   11/7/2000   02:44   509,072   Rdr.sys     Alpha

WORKAROUND

To work around this issue, increase the MaxMpxCt setting on the server as described in the following Microsoft Knowledge Base article:

141709 Limit of 49 Named Pipe Connections from a Single Workstation

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB268817
©2004 Microsoft Corporation. All rights reserved.