You cannot manually reset connections between domain controllers and global catalog servers in a Windows 2000-based forest

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. You have multiple global catalog servers in a Windows 2000-based forest, you cannot manually reset connections between domain controllers and global catalog servers.Therefore, responses from global catalog servers may be very slow if the connections between global catalog servers and domain controllers are not highly available. This situation may occur when the following conditions are true:
  • The global catalog servers are connected to the domain controllers by wide area network (WAN) connections.
  • The connections between global catalog servers and the domain controllers are overloaded.
In this situation, you may experience various performance issues with the Active Directory authentication. For example, the client users may wait for a long time when they are logging on to the domain.
This hotfix enables you to manually reset connections between global catalog servers and domain controllers. After you apply this hotfix on the domain controllers, you can manually reset the connections between global catalog servers and domain controllers. Then the cache in the domain controllers is flushed. To do this, set the invalidateGCConnection attribute of the rootDSE object to a value of 1 by using the Active Directory Service Interfaces (ADSI). To do this, follow these steps:
  1. Paste the following script to a text file. Then, save the text file by using the name of Resetgc.vbs.
    ' check the parametersSet oArgs = WScript.ArgumentsIf oArgs.Count <> 3 Then    WScript.Echo "Wrong number of arguments"    WScript.Echo "Usage:  cscript resetgc.vbs servername domainname\username password"    WScript.Quit(1)End If' Execute the commandSet LDAPNameSpace = GetObject( "LDAP:" )Set Root= LDAPNameSpace.OpenDSObject( "LDAP://" & oArgs(0) & "/RootDSE", oArgs(1), oArgs(2), ADS_SECURE_AUTHENTICATION )Root.Put "invalidateGCConnection", "1"Root.SetInfoWScript.Echo "The global catalog connection on " & oArgs(0) & " has been invalidated." 
  2. Open a command prompt, and then move to the path where you saved the Resetgc.vbs file in step1.
  3. Run the following command at the command prompt:

    cscript resetgc.vbs <ServerName> <DomainName>\<Username> <Password>

    Note <ServerName> is the computer name of the domain controller. <DomainName> is the name of the domain. <Username> is the username of a domain administrator. <Password> is the password for the user name that you specified.

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 this hotfix, you must have Windows 2000 Service Pack 3 (SP3) or a later service pack installed.

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 file attributes) 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.
File nameFile versionFile sizeDateTimePlatform
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more 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 more information about the terms that are used to describe software updates, 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: 891581 - Last Review: 11/02/2013 17:43:00 - Revision: 4.0

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbautohotfix kbexpertiseinter kbbug kbfix kbHotfixServer kbqfe kbwin2000presp5fix KB891581