WINDOWS SERVER - DFS - DFSR Inconsistent Configuration Detected

1. Home
2. Support Home
3. Knowledge Base Article

Print Email English

• Česky
• Dansk
• Deutsch
• English
• Español
• Suomi
• Français
• Italiano
• 日本語
• 한국어
• Nederlands
• Norsk
• Polski
• Português
• Русский
• Svenska
• Türkçe
• 繁體中文
• Українська
• 简体中文

Windows Server: DFS - DFSR inconsistent configuration detected Table of Contents Detailed Article Symptoms Cause Resolution Affected Products Provide Feedback

Summary: This article details an issue where you get an error when running a DFS Diagnostic report on a given replication group, there is an error, with accompanying Event ID 6004.

Detailed Article

Symptoms

Cause

Resolution

Affected Products

Provide Feedback Please select a product to check article relevancy This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article. Check out other resources Identify Your Product

Symptoms

When running a DFS Diagnostic report on a given replication group, there is an error, with accompanying Event ID 6004, stating:

The DFS Replication service detected a conflict between two or more nTDSConnection objects while polling Active Directory Domain Services for configuration information. The conflict detected on <connection object distinguished name> was resolved by using <connection object distinguished name>"

Cause

There are conflicting connection objects which must be reconciled.

Resolution

Steps:

1. Follow the advice of the event and delete the first replication connection, or connections that were resolved by the latter connection.

2. From Server Manager click Tools and choose ADSI Edit.

3. When it opens, right-click ADSI Edit, choose Connect To.

4. This brings up the following screen. Choose the Configuration Naming Context and click OK.

5. Now delete the connection objects listed in the event where the conflict was detected while making sure to leave the object after "was resolved by using" alone, as it is the good or working connection. An example of a connection object would be:

   "CN=b707b5f7-3c2c-491e-b7ee-537963299830,CN=NTDS Settings,CN=CustomerDC, CN=Servers,CN=Site1,CN=Sites,CN=Configuration,DC=domain,DC=com"

   Using the example, in ADSI Edit, browse to Sites-Site1- Servers- CustomerDC-NTDS Settings and the connection object for CN=b707b5f7-3c2c-491e-b7ee-537963299830 would be over in the right pane. The screen would look similar to this:

6. In this case, there should be multiple connection objects. That is what is causing the issue. If there are not multiple objects in the right pane, stop and consider an alternative root cause.

7. Assuming there are multiple connection objects, using the example we would right-click the object for CN=b707b5f7-3c2c-491e-b7ee-537963299830 and choose delete. This would leave the good or valid connection object in place.

8. Repeat the process for any additional connection objects mentioned after "The conflict detected on.." in the event but as previously stated, leave the "was resolved by using…." Connection in place.

Affected Products

Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022

Products

PowerEdge M640, PowerEdge M640 (for PE VRTX), PowerEdge MX740C, PowerEdge MX750c, PowerEdge MX760c, PowerEdge MX840C, PowerEdge R240, PowerEdge R250, PowerEdge R260, PowerEdge R340, PowerEdge R350, PowerEdge R360, PowerEdge R440, PowerEdge R450 , PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515, PowerEdge R6525, PowerEdge R660, PowerEdge R660xs, PowerEdge R6615, PowerEdge R6625, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R760, PowerEdge R760XA, PowerEdge R760xd2, PowerEdge R760xs, PowerEdge R7615, PowerEdge R7625, PowerEdge R840, PowerEdge R860, PowerEdge R940, PowerEdge R940xa, PowerEdge R960, PowerEdge T140, PowerEdge T150, PowerEdge T160, PowerEdge T340, PowerEdge T350, PowerEdge T360, PowerEdge T440, PowerEdge T550, PowerEdge T560, PowerEdge T640 ... View More View Less

Article Properties

Article Number: 000137298 Article Type: Solution Last Modified: 05 Sept 2025 Version: 9

Find answers to your questions from other Dell users

Visit Community

Support Services

Check if your device is covered by Support Services. Check Support Status

Article Properties

Article Number: 000137298 Article Type: Solution Last Modified: 05 Sept 2025 Version: 9

Find answers to your questions from other Dell users

Visit Community

Support Services

Check if your device is covered by Support Services. Check Support Status