Active Directory Faulted
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Andrew Walker December 28, 2020 at 9:37 PM
Yes, that can have an impact. It would be a much better practice to have at least one of your domain controllers on a separate physical server than the TrueNAS server if it is to be joined to the AD domain.
In this case we failed to join because we could not find the DC:
middlewared.service_exception.CallError: [EFAULT] Failed to join domain: failed to lookup DC info for domain '<redacted>.INTERNAL' over rpc: No logon servers are currently available to service the logon request.
In the bigger picture, it is best to have at least two domain controllers for a given Active Directory domain, and at least one of them should not be hosted on the NAS appliance, and both should be set as the nameservers for the NAS. This is to ensure proper failover if one of the DCs goes down. Time must also be stable on the DCs, and as a general principal your Domain Controllers should only ever be deployed on a well-vetted and stable virtualization platform.
Henrik Brekke December 28, 2020 at 6:47 PMEdited
Yes, the domain controller is hosted on a VM (on the TrueNAS), should that have an impact?
Andrew Walker December 28, 2020 at 6:43 PM
Is the domain controller for this AD domain hosted on the TrueNAS server?
Details
Details
Assignee
Reporter
Impact
Components
Fix versions
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
When i am trying to add the AD as a directory service there is no warning/errors when i am saving the credentials. (I've tried with both the Admin account and with another account with admin previlages)
When i open the "monitor" it says Active Directory : FAULTED
(The domain controller respons to ping)