Univention Bugzilla – Bug 37460
AD-Member setup: join fails if AD NETBIOS domain name is unusual
Last modified: 2017-03-10 14:09:28 CET
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.
Microsoft ADs with dissenting NETBIOS and DNS domain names aren't unusual, especially if they are older, were migrated from Windows NT once or if the DNS domain name is longer than 15 characters. Since it is not possible to specify a dissenting NETBIOS domain name with UCS 4.0 (Bug 36991) during installation, this breaks AD Connection (Member Mode) for all those Microsoft ADs.
also reported in 2015020621000463 Setup: existing AD-Domain with following settings: ADS Domain: example-domain.com Netbios Workgroup: exdo Join an UCS AD-Member into AD-Domain failed with error message in join.log: Failed to join domain: Invalid configuration ("workgroup" set to 'example-domai', should be 'exdo') and configuration modification was not requested ERROR: Failed to join to AD DC via net ads join. Please check your Samba DCs and your DNS and WINS configuration The main problem is, that no NETBIOS name could be set during the installation (see Bug#36991). Workaround: Start with UCS 3.2-4, set the alternate Netbios name in setup and install AD-Connector as AD member from appcenter.
(In reply to Tobias Birkefeld from comment #2) > Workaround: > Start with UCS 3.2-4, set the alternate Netbios name in setup and install > AD-Connector as AD member from appcenter. Workaround: You can set the NETBIOS domain during the installation. Press ALT-F2 before starting the domain setup and set the windows/domain: chroot /target /bin/bash ucr set --force windows/domain=DOMAIN See Ticket #2015012821000012
also reported in 2015061921000191 workaround is clear, but not a nice way for customers.
I fixed it in system setup: 4.0-2-errata: r62221 4.1: r62222 YAML: r62223
Verified: * Works * Advisory: Ok
<http://errata.univention.de/ucs/4.0/251.html>