Directory Service Stops Responding on Heavily Loaded Domain Controller (313657)


The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
This article was previously published under Q313657

SYMPTOMS

A heavily loaded domain controller may stop responding to client requests. You may be able to confirm a network connection to the domain controller by using the Ping.exe utility, but when a client tries to view or connect to a share, you receive network error 58.

CAUSE

This behavior may occur if the Directory Service stops responding because of a thread blocking issue. In certain situations, a thread that holds the NTDSA!csHiddenDBPOS function may be waiting for the execution of another thread that is, in turn, waiting for the execution of this thread that holds the NTDSA!csHiddenDBPOS function. This creates a deadlock in the Directory Service and causes all inbound calls to become backlogged.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English-language version of this fix should have the following file attributes or later:
   Date         Time   Version           Size     File name
   -----------------------------------------------------------
   04-Dec-2001  01:03  5.0.2195.4685     123,664  Adsldp.dll       
   04-Dec-2001  01:03  5.0.2195.4628     130,320  Adsldpc.dll      
   04-Dec-2001  01:03  5.0.2195.4016      62,736  Adsmsext.dll     
   04-Dec-2001  01:03  5.0.2195.4653     356,112  Advapi32.dll     
   04-Dec-2001  01:03  5.0.2195.4571      82,704  Cmnquery.dll     
   04-Dec-2001  01:03  5.0.2195.4141     133,904  Dnsapi.dll       
   04-Dec-2001  01:03  5.0.2195.4379      91,408  Dnsrslvr.dll     
   04-Dec-2001  01:03  5.0.2195.4534      41,744  Dsfolder.dll     
   04-Dec-2001  01:03  5.0.2195.4534     156,944  Dsquery.dll      
   04-Dec-2001  01:03  5.0.2195.4574     110,352  Dsuiext.dll      
   04-Dec-2001  01:05  5.0.2195.4685     521,488  Instlsa5.dll     
   04-Dec-2001  01:03  5.0.2195.4630     145,680  Kdcsvc.dll       
   27-Nov-2001  00:33  5.0.2195.4680     199,440  Kerberos.dll     
   04-Sep-2001  16:32  5.0.2195.4276      71,024  Ksecdd.sys
   27-Nov-2001  01:55  5.0.2195.4685     503,568  Lsasrv.dll       
   27-Nov-2001  01:55  5.0.2195.4685      33,552  Lsass.exe        
   27-Nov-2001  00:32  5.0.2195.4680     107,280  Msv1_0.dll       
   04-Dec-2001  01:03  5.0.2195.4594     306,960  Netapi32.dll     
   04-Dec-2001  01:03  5.0.2195.4686     359,184  Netlogon.dll     
   04-Dec-2001  01:03  5.0.2195.4720     913,680  Ntdsa.dll        
   04-Dec-2001  01:03  5.0.2195.4627     387,856  Samsrv.dll       
   04-Dec-2001  01:03  5.0.2195.4583     128,784  Scecli.dll       
   04-Dec-2001  01:03  5.0.2195.4600     299,792  Scesrv.dll       
   04-Dec-2001  01:03  5.0.2195.4600      48,400  W32time.dll      
   06-Nov-2001  19:43  5.0.2195.4600      56,592  W32tm.exe        
   04-Dec-2001  01:03  5.0.2195.4684     125,712  Wldap32.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbDirServices kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB313657
©2004 Microsoft Corporation. All rights reserved.