GC Adds Non-Domain NCs as Read-Only Replicas When a Windows 2000 DC Replicates with a Whistler DC

Article translations Article translations
Article ID: 289172 - View products that this article applies to.
This article was previously published under Q289172
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

When a Windows 2000-based domain controller (DC) replicates with a Whistler-based domain controller, the Windows 2000 global catalog (GC) attempts to add read-only replicas of Whistler non-domain naming contexts (NCs) as if they are domain NCs. Because non-domain NCs generally contain more volatile data than domain NCs do, there is an excess of replication traffic to the Windows 2000 GC.

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

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows 2000.

This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

Whistler introduces a concept of non-domain NCs. In order for Whistler-based DCs and Windows 2000-based DCs to interoperate effectively, Windows 2000-based DCs need a small localized change to the Knowledge Consistency Checker (KCC) to prevent their replicating these non-domain NCs to their global catalogs.

Properties

Article ID: 289172 - Last Review: October 23, 2013 - Revision: 3.2
APPLIES TO
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB289172

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com