It takes up to one minute to complete an Active Directory task on your Windows 2000 server

This article has been archived. It is offered "as is" and will no longer be updated.
When you try to view the properties of an Active Directory object on your Microsoft Windows 2000 server, you may have to wait up to one minute for the property information to appear. This problem may also occur when you try to complete any other task in Active Directory. For example, you try to join a member server to Active Directory.
This problem may occur if the DNS scavenger thread inside the Lsass.exe program is running when you try to complete the Active Directory task. The DNS scavenger thread starts periodically to update the global DNS list that Lsass.exe uses. When the DNS scavenger thread starts, the DNS scavenger acquires the NlGlobalDnsCritSect sync-object and holds it until the scavenging is completed.During DNS scavenging, the DNS scavenger uses your network to contact each global DNS list element. The time it takes to complete the scavenging depends on the length of the global DNS lists and the performance of your network. During this time, other Netlogon requests that must access the global DNS list are not completed until the NlGlobalDnsCritSect sync-object becomes available.

Lsass.exe manages the local security authority domain authentication and Active Directory. Lsass.exe handles authentication for both the client and the server, and it governs the Active Directory engine.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply the hotfix, you must have Microsoft Windows 2000 Service Pack 3 (SP3) or later.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version        Size    File name   ----------------------------------------------------------   15-Dec-2003  19:34  5.0.2195.6824    124,688  Adsldp.dll          15-Dec-2003  19:34  5.0.2195.6824    132,368  Adsldpc.dll         15-Dec-2003  19:34  5.0.2195.6824     63,760  Adsmsext.dll        15-Dec-2003  19:34  5.0.2195.6876    381,712  Advapi32.dll        15-Dec-2003  19:34  5.0.2195.6866     69,904  Browser.dll         15-Dec-2003  19:34  5.0.2195.6824    136,464  Dnsapi.dll          15-Dec-2003  19:34  5.0.2195.6876     96,528  Dnsrslvr.dll        15-Dec-2003  19:34  5.0.2195.6866     47,376  Eventlog.dll        15-Dec-2003  19:34  5.0.2195.6871    148,240  Kdcsvc.dll          08-Dec-2003  23:28  5.0.2195.6881    206,096  Kerberos.dll        21-Sep-2003  00:32  5.0.2195.6824     71,888  Ksecdd.sys   08-Dec-2003  23:30  5.0.2195.6881    511,248  Lsasrv.dll          08-Dec-2003  23:30  5.0.2195.6881     33,552  Lsass.exe           17-Oct-2003  00:33  5.0.2195.6866    114,960  Msv1_0.dll          15-Dec-2003  19:34  5.0.2195.6866    307,984  Netapi32.dll        15-Dec-2003  19:34  5.0.2195.6883    361,744  Netlogon.dll        15-Dec-2003  19:34  5.0.2195.6874    931,600  Ntdsa.dll           15-Dec-2003  19:34  5.0.2195.6876    392,464  Samsrv.dll          15-Dec-2003  19:34  5.0.2195.6824    113,936  Scecli.dll          15-Dec-2003  19:34  5.0.2195.6824    259,856  Scesrv.dll          06-Nov-2003  22:29  5.0.2195.6870  5,847,552  Sp3res.dll          09-Oct-2003  02:18            6,656  Spmsg.dll           09-Oct-2003  02:18          140,800  Spuninst.exe        15-Dec-2003  19:34  5.0.2195.6824     48,912  W32time.dll         21-Sep-2003  00:32  5.0.2195.6824     57,104  W32tm.exe           15-Dec-2003  19:34  5.0.2195.6869    126,224  Wldap32.dll         15-Dec-2003  19:44                    14,242   09-Oct-2003  02:18           22,016  Spcustom.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New File Naming Schema for Microsoft Windows Software Update Packages
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

Article ID: 824037 - Last Review: 10/26/2013 19:13:00 - Revision: 2.6

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB824037