Dcdiag.exe Issues Incorrect "Topology Disconnected" Error Messages

This article was previously published under Q320063
This article has been archived. It is offered "as is" and will no longer be updated.
When you run the Domain Controller Diagnostics tool (Dcdiag.exe) to test your topology, the tool may report that some servers cannot get changes.

For example, running the dcdiag /test:topology command erroneously reports indirect or transitive replication partners that are not authoritative for a container as disconnected if the testing server is also not authoritative for that container. Therefore, if a server is a global catalog server (it is not authoritative), replication partners that are also global catalog servers are listed as disconnected in the primary test listing.

Additionally, any domain controller that is an authoritative master (that has a writable copy) of a particular container, or is a non-transitive (direct replication) partner of the testing server passes the topology test and is not listed in the list of disconnected servers.

The error messages are similar to:
Doing primary tests
Testing server: THIS\THISSERVER
Starting test: Topology
Downstream topology is disconnected for DC=THIS,DC=DOMAIN,DC=COM.
These servers can't get changes from home server THISSERVER:
......................... THISSERVER failed test Topology
Under the conditions that are listed in this article, the Directory Services API DsReplicaSyncAll function generates the DS_REPSYNCALL_SERVER_UNREACHABLE error. This occurs if the DS_REPSYNCALL_PUSH_CHANGES_OUTWARD bit is set in the ulFlags parameter during a call to DsReplicaSyncAll.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft 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

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. The English version of this fix 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   ------------------------------------------------------   28-May-2002  12:16  5.0.2195.5834  57,616  Ntdsapi.dll				

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 Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

Article ID: 320063 - Last Review: 10/24/2013 11:07:07 - Revision: 3.7

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbdirservices kbwin2ksp4fix kbbug kberrmsg kbfix kbwin2000presp4fix KB320063