Univention Bugzilla – Bug 42918
App appliance cant join as additional ad member
Last modified: 2018-03-15 08:51:10 CET
***.intern: Authentication failed while contacting: [Errno 111] Verbindungsaufbau abgelehnt Version: 4.1-3 errata234 (Vahr) Remark: wo liegt hier das Problem ? → Before joining a DC Slave UCS System a check if the master has an activated license is done. If the UMC-Server of the master isn't reachable this error occurs. This is very similar to Bug #42910 and should be solved together.
Reported again, 4.1-3 errata239 (Vahr) win2k12.sha.local: Authentication failed while contacting: [Errno 104] Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
Version: 4.1-3 errata239 (Vahr) Remark: Windows 2012 R2 Domain Controller Authentication failed while contacting: [Errno 110] Die Wartezeit für die Verbindung ist abgelaufen
Version: 4.1-3 errata239 (Vahr) Remark: One UCS Kopano-Core system is already installed as an AD member server. When installing the second UCS server this "connection refused/authentication error" persists. During installation it was selected to "Join existing AD domain". Tried even the option of "Join existing USC domain" which ended in a similar error.
Version: 4.1-3 errata239 (Vahr)
Reported again, 4.1-4 errata420 (Vahr)
Reported again, 4.1-4 errata420 (Vahr) Authentication failed while contacting: [Errno 101] Network is unreachable
Reported again, 4.1-4 errata420 (Vahr) Remark: Unable to finish setup due to authentication error. Account used to join server to domain is correct. Even when I press the finish button I can't even log onto the console as it doesn't recognize the root password I've entered in? Any help would be great. Note: this is a VM server which is on the correct VLan network (same as all other servers). Have tried dhcp and static ip's. Not sure if this is the issue or not?
The problem happens in domain_has_activated_license() from base/univention-system-setup/umc/python/setup/util.py.
This error affects only UCS appliances on non-DC-Master roles during the initial configuration if e.g. the Master is not available. I think the only thing we can improove here is the error message.
Mark all bugs with a user pain > 0.3 as errata bugs.
Reported again, 4.1-4 errata439 (Vahr)
This is obsolete by Bug #44995. *** This bug has been marked as a duplicate of bug 44995 ***
Remark: cant join domain
Version: 4.1-4 errata439 (Vahr) Remark: cant join owncloud boxed ;( I tried like 10 times, different VM servers and even my local vmware workstation, no success
Version: 4.1-4 errata439 (Vahr) #2017080921000211
(In reply to Florian Best from comment #3) > Version: 4.1-3 errata239 (Vahr) > > Remark: One UCS Kopano-Core system is already installed as an AD member > server. > When installing the second UCS server this "connection > refused/authentication error" persists. > > During installation it was selected to "Join existing AD domain". > Tried even the option of "Join existing USC domain" which ended in a similar > error. This was not fixed in bug 44995 :( The problem happens if there is already one ucs system joined into an ad domain and a user tries to join an additional ucs system (an app appliance) into that domain. The error happens because the licence check is done against the windows dc and not against the ucs master. Relevant file: base/univention-system-setup/umc/python/setup/util.py The ucs master can be found with the SRV record: _domaincontroller_master._tcp.$DOMAIN. See for example is_ucs_domain(). If something like a get_ucs_master() function gets added it might make sense to fix bug 45170 as well. As a workaround I had success using the ucs master as the dns and choosing "Join existing ucs domain". Note: As described in bug 44995 non master app appliances aren't working that well at the moment. So that should be fixed first.
*** Bug 43231 has been marked as a duplicate of this bug. ***
*** Bug 45246 has been marked as a duplicate of this bug. ***
Authentication failed while contacting: [Errno 110] Connection timed out Version: 4.1-4 errata439 (Vahr) #2017090421001093
*** This bug has been marked as a duplicate of bug 43745 ***
OK, duplicate
Nothing to release