Bug 43784 – AD-Member setup: join fails if AD NETBIOS domain name is unusual

Bug 43784 - AD-Member setup: join fails if AD NETBIOS domain name is unusual


Summary:	AD-Member setup: join fails if AD NETBIOS domain name is unusual

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Setup wizard
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:	37460
Blocks:
	Show dependency tree / graph

Reported:	2017-03-10 12:51 CET by Nico Stöckigt
Modified:	2019-01-03 07:20 CET (History)
CC List:	5 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?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017030621000252
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nico Stöckigt

2017-03-10 12:51:36 CET

+++ This bug was initially created as a clone of Bug #37460 +++

When an AD-Server has a non-default NETBIOS domain name like

 NETBIOS domain: FOOBAR0
 DNS domainname: FooBar.com

the setup of an AD-Member (Master) fails with an empty error message.

This seems to be caused by a failure of "net ads join" in 26univention-samba.inst:


+ net ads join -UAdministrator%Univention.1 machinepass=QFLa7a7IIC363XYPbk1k
Failed to join domain: Invalid configuration ("workgroup" set to 'FOOBAR', should be 'FOOBAR0') and configuration modification was not requested


So we need to lookup the NETBIOS domain of the AD-Server and set UCR windows/domain accordingly. After doing this manually, the joinscript succeeded.

The situation came up accidentally, because my test AD-Server found that the netbios domainname "FOOBAR" was already used by another domain/server in my subnet. In this case AD "dcpromo" suggest a different NETBIOS name.

Comment 1 Nico Stöckigt

2017-03-10 12:51:47 CET

I actually had this in a customer environment with UCS 4.1-4 errata406.

The Netbios-Domain differed from the AD-Domain (first part).
After changing
 - ucr set windows/domain="OTHER"
 - udm settings/sambadomain modify --dn "sambaDomainName=WRONG,cn=samba,dc=domain,dc=tld" --set "name=OTHER"
everything works fine...

Comment 2 Stefan Gohmann

2019-01-03 07:20:51 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.