AD error repeats
Description
Problem/Justification
None
Impact
None
Activity
Show:
Andrew Walker February 11, 2022 at 7:33 PM
Newer versions have more verbose error message:
```
netads = await run(cmd, check=False)
if netads.returncode != 0:
err_msg = netads.stderr.decode().strip()
if err_msg == "Didn't find the ldap server!":
raise CallError(
'Failed to discover Active Directory Domain Controller '
'for domain. This may indicate a DNS misconfiguration.',
errno.ENOENT
)
raise CallError(netads.stderr.decode())
```
Andrew Walker February 10, 2022 at 4:05 PM
Do you have DNS properly configured? This is usually a DNS error.
User Configuration Error
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Triage Team
Triage TeamReporter
Zack
ZackLabels
Components
Fix versions
Affects versions
Priority
More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created February 10, 2022 at 3:55 PM
Updated July 6, 2022 at 8:59 PM
Resolved February 11, 2022 at 7:33 PM
When I was setting up AD on 22.02-RC.2, I failed to connected, whereupon I saw this error text
"ads_connect: No logon servers are currently available to service the logon request. ads_connect: No logon servers are currently available to service the logon request. Didn't find the ldap server! "