Do I really have to rejoin the client to AD after changing samba security to ADS? I'm not using samba "net join" and no winbind for AD binding. I've created the AD machine account with realm and I'm using sssd for authentication to AD DC.
BTW "realm" changed my "security = ADS" in smb.conf to "security = user"....
However, I could reproduce the smb crash anytime when
security = ADS
is set. It doesn't matter if I specify "kerberos method" or not.
When set to
security = user
and disabled
# kerberos method = secrets and keytab
smb is not crashing anymore but I also cannot authenticate with my AD user account (using sssd).
Enabling
kerberos method = secrets and keytab
and
security = user
let's smb crash too.
Do I really have to rejoin the client to AD after changing samba security to ADS? I'm not using samba "net join" and no winbind for AD binding. I've created the AD machine account with realm and I'm using sssd for authentication to AD DC.
BTW "realm" changed my "security = ADS" in smb.conf to "security = user"....
However, I could reproduce the smb crash anytime when
security = ADS
is set. It doesn't matter if I specify "kerberos method" or not.
When set to
security = user
and disabled
# kerberos method = secrets and keytab
smb is not crashing anymore but I also cannot authenticate with my AD user account (using sssd).
Enabling
kerberos method = secrets and keytab
and
security = user
let's smb crash too.