We use cookies on this website. To find out more about cookies and how they are used on this website, see our Privacy Policy.
By clicking ‘Continue’, you hereby agree with our use of cookies.

Knowledge Base

How to Deal with Cannot Join AD: Issues Related to DNS Server Settings?

Last modified date: Thu, 24 Oct 2024 15:57:45 GMT+8

Symptom

The user can ping the DNS server and AD server, but the GUI displays the error message: "CTLR has connected to the DNS server, but the DNS entry is wrong. The KDC server is not found."
The KDC server is not found

Diagnosis

To diagnose this issue, follow these steps:

  1. Navigate to EonOne > Settings > Access.
  2. Under the DNS Server section, ensure that only the DNS Server which needs to be linked is listed.

This issue typically occurs when multiple DNS nameservers are configured, leading to incorrect DNS entries and the inability to find the Key Distribution Center (KDC) server.
find the Key Distribution Center (KDC) server

Solution

To resolve this issue, follow these steps:

  • Remove Unnecessary DNS Nameservers:
    1. Access the EonOne management interface.
    2. Go to Settings > Access.
    3. Under the DNS Server section, remove all DNS nameservers except for the one necessary for the AD server.
  • Verify DNS and AD Server Configuration:
    1. Ensure that the DNS server entry is correct and points to the proper AD server IP.
    2. Confirm that the AD server IP is correctly configured and reachable from the storage system.

By keeping only the necessary AD server IP and ensuring the correct DNS configuration, the system should be able to properly connect to the AD server, resolving the error message and allowing successful integration with Active Directory.

Was this article helpful?Yes | No

Thank you for your feedback!

Do you have any other feedback for this article?

{{ vm.showErrorMessage }}