Comment 5 for bug 1794537

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Can you elaborate a bit on how you are joining the domain, and the output you are getting? The upstream bug and this one are not showing that particular detail, they only say that "net ads join fails".

I'm on bionic and I'm using "net ads join -k", after having obtained a ticket for the realm's Administrator.

Something like this:
root@bionic:~# kinit Administrator
Password for <email address hidden>:
root@bionic:~# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: <email address hidden>

Valid starting Expires Service principal
10/18/18 18:40:14 10/19/18 04:40:14 <email address hidden>
 renew until 10/19/18 18:40:12
root@bionic:~# net ads join -k
Using short domain name -- LOWTECH
Joined 'BIONIC' to dns domain 'lowtech.internal'
root@bionic:~# echo $?
0

I can confirm in windows' "Active Directory Users and Computers" that the computer record is there. This is a 2016 AD Server, btw.

At first I had a dns update error, like described in https://wiki.samba.org/index.php/Troubleshooting_Samba_Domain_Members#No_DNS_domain_configured._Unable_to_perform_DNS_Update.

I then added the fqdn of this host to /etc/hosts and repeated the join, and now it works. And DNS is working too.