Bug 44478 - Give the user more information how to handle "Could not connect to AD Server" messages
Give the user more information how to handle "Could not connect to AD Server"...
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.3-0-errata
Assigned To: Arvid Requate
Felix Botner
:
Depends on:
Blocks: 47091
  Show dependency treegraph
 
Reported: 2017-04-27 12:18 CEST by Florian Best
Modified: 2018-05-28 12:06 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.309
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number: 2018031921002055, 2018050721000012, 2018031521000662, 2018021121000019, 2018021421000451, 2018011221000742, 2017102821000313, 2017042421000494, 2017042621000703, 2017042821000218, 2017043021000348, 2017070521001022, 2017080721000358
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2017-04-27 12:18:06 CEST
Version: 4.1-4 errata410 (Vahr)

Einrichten der Active-Directory-Verbindung: Eine Verbindung zum AD-Server Server2012.*****.LOCAL konnte nicht hergestellt werden. Bitte überprüfen Sie, ob die angegebene Adresse
korrekt ist.

Configuring Active Directory connection: Could not connect to AD Server ****.com. Please verify that the specified address is correct.
Comment 1 Arvid Requate univentionstaff 2017-04-28 12:43:17 CEST
As discussed yesterday, we should ask the customer to provide logfiles. Or: We should ask to provide the email address, so we can at least ask for a logfile in case it would be useful. In this case it's essential.
Comment 2 Florian Best univentionstaff 2017-04-28 14:20:33 CEST
Reported again, 4.2-0 errata4 (Lesum)

Remark: kann nicht ohne fehler an der active directory beitraten
Comment 5 Florian Best univentionstaff 2017-07-07 16:45:52 CEST
Reported again, 4.1-4 errata439 (Vahr)
Comment 6 Florian Best univentionstaff 2017-08-15 09:41:02 CEST
4.1-4 errata445 (Vahr)
Comment 7 Johannes Keiser univentionstaff 2018-01-15 16:16:48 CET
Version: 4.2-3 errata262 (Lesum)

Einrichten der Active-Directory-Verbindung: Eine Verbindung zum AD-Server ***.local konnte nicht hergestellt werden. Bitte überprüfen Sie Benutzername und
Password.
Comment 8 Johannes Keiser univentionstaff 2018-02-16 13:54:15 CET
Reported again: Version: 4.2-3 errata284 (Lesum)
Comment 9 Johannes Keiser univentionstaff 2018-02-16 14:04:14 CET
Reported again: Version: 4.2-3 errata284 (Lesum)
Could not connect to AD Server ***. Please verify that the specified address is correct.
Request: check_domain
Comment 10 Johannes Keiser univentionstaff 2018-03-16 12:00:53 CET
Reported again: Version: 4.3-0 errata0 (Neustadt)

Remark: Beitritt zur AD-Domäne eines Windows Server 2016 scheitert zum wiederholten Male.
Comment 11 Arvid Requate univentionstaff 2018-03-16 12:13:22 CET
> Reported again: Version: 4.3-0 errata0 (Neustadt)
> 
> Remark: Beitritt zur AD-Domäne eines Windows Server 2016 scheitert zum
> wiederholten Male.

See Comment 1, we *need* more info. If we don't have it, we must create a way to obtain it, otherwise, eternally adding "+1" won't get us nowhere.
Comment 12 Stefan Gohmann univentionstaff 2018-03-16 13:05:32 CET
(In reply to Arvid Requate from comment #11)
> See Comment 1, we *need* more info. If we don't have it, we must create a
> way to obtain it, otherwise, eternally adding "+1" won't get us nowhere.

The +1 helps us to identify if it still happens with newer versions.

Anyway, I've changed the scope of the bug.
Comment 13 Arvid Requate univentionstaff 2018-03-22 20:10:46 CET
87528b94f0 | Improve debug output in lib.admember.lookup_adds_dc()
c813ce9c08 | Output exception details in check_domain and admember_join
d7772a9603 | Advisories
869997838a | Add package versions to advisories
Comment 14 Felix Botner univentionstaff 2018-03-27 13:34:15 CEST
OK - ad connector setup
OK - ad member setup
OK - YAML
Comment 16 Johannes Keiser univentionstaff 2018-05-25 19:05:00 CEST
Version: 4.2-3 errata342 (Lesum)

Configuring Active Directory connection: Could not connect to AD Server ***. Please verify that the specified address is correct.


Version: 4.3-0 errata0 (Neustadt)
Remark: synology diskstation as AD controller.  Trying to join UCS as domain member.  It fails

Configuring Active Directory connection: Could not connect to AD Server ***. Please verify that username and password are correct.