Hi all,
I’m running linuxmuster 7.3. I had upgraded successfully with no issue and have been running for the past 1 month. However, after the ubuntu update 3 days ago I started facing issue of joining domain. It says
realm: Failed to join domain
Also, when I tried to click on the shared folders I get this error.
Could not load directory :
There's a problem with the kerberos authentication : Failed to authenticate with server: SpnegoError (1): SpnegoError (16): Operation not supported or available, Context: Retrieving NTLM store without NTLM_USER_FILE set to a filepath, Context: Unable to negotiate common mechanism
This is the error I get when I run linuxmuster-linuxclient7 setup
[INFO] #### Joining domain ad.cdsc.ac.th ####
* Resolving: _ldap._tcp.ad.cdsc.ac.th
* Performing LDAP DSE lookup on: 10.10.10.1
* Successfully discovered: ad.cdsc.ac.th
Passwort für global-admin:
* Unconditionally checking packages
* Resolving required packages
* LANG=C /usr/sbin/adcli join --verbose --domain ad.cdsc.ac.th --domain-realm AD.CDSC.AC.TH --domain-controller 10.10.10.1 --login-type user --login-user global-admin --stdin-password
* Using domain name: ad.cdsc.ac.th
* Calculated computer account name from fqdn: PC-00054
* Using domain realm: ad.cdsc.ac.th
* Sending NetLogon ping to domain controller: 10.10.10.1
* Received NetLogon info from: lmnv7.ad.cdsc.ac.th
* Wrote out krb5.conf snippet to /var/cache/realmd/adcli-krb5-2NW7oW/krb5.d/adcli-krb5-conf-2ZBITO
! Couldn't authenticate as: global-admin@AD.CDSC.AC.TH: Client 'global-admin@AD.CDSC.AC.TH' not found in Kerberos database
adcli: couldn't connect to ad.cdsc.ac.th domain: Couldn't authenticate as: global-admin@AD.CDSC.AC.TH: Client 'global-admin@AD.CDSC.AC.TH' not found in Kerberos database
! Failed to join the domain
realm: Dem Bereich konnte nicht beigetreten werden: Failed to join the domain
[ERROR] Failed! Did you enter the correct password?
================================================================================
The setup FAILED, see previous errors!
Plase check your configuration and try again.
================================================================================
We use only Ubuntu and this has never happened before. It only happened after the server had to be restarted after an update.