Help with Samba and Kerberos Integration Issue After System Crash
by julius_c from LinuxQuestions.org on (#6HR6D)
Hello everyone,
I'm facing a challenging issue with Samba and Kerberos integration in an Active Directory environment and need your expert advice.
Background:
Running Samba version 4.15.13 on Ubuntu.
After a system crash, several logs were corrupted.
The krb5.keytab file is missing, and attempts to recreate it using samba-tool domain exportkeytab have been unsuccessful.
The kinit command behaves inconsistently: it recognizes an incorrect password but indicates the user is not found in the Kerberos database when the correct password is used.
The user is indeed present in the database, as confirmed by samba-tool user show Administrator.
Attempts:
Verified file system integrity and permissions.
Checked Samba and system logs, but many were corrupted due to the crash.
Restarted Samba services and tried various configurations without success.
I would greatly appreciate any insights or suggestions on how to resolve this. It seems like a complex issue possibly involving Samba's internal state or Kerberos integration.
Thank you in advance!
I'm facing a challenging issue with Samba and Kerberos integration in an Active Directory environment and need your expert advice.
Background:
Running Samba version 4.15.13 on Ubuntu.
After a system crash, several logs were corrupted.
The krb5.keytab file is missing, and attempts to recreate it using samba-tool domain exportkeytab have been unsuccessful.
The kinit command behaves inconsistently: it recognizes an incorrect password but indicates the user is not found in the Kerberos database when the correct password is used.
The user is indeed present in the database, as confirmed by samba-tool user show Administrator.
Attempts:
Verified file system integrity and permissions.
Checked Samba and system logs, but many were corrupted due to the crash.
Restarted Samba services and tried various configurations without success.
I would greatly appreciate any insights or suggestions on how to resolve this. It seems like a complex issue possibly involving Samba's internal state or Kerberos integration.
Thank you in advance!