search for: pbeqj9zr

...work. It seems like the id of the user isn't passed through or looked up correctly after Kerberos auth, and the user is labelled as a guest user. Guest users are mapped to bad user in samba config. Here's a bit of logging when the Windows client tries to access a share: https://pastebin.com/pbEqj9ZR Configs; smb.conf: https://pastebin.com/XfeVTCDE sssd.conf: https://pastebin.com/Z57rRwBw krb5.conf: https://pastebin.com/JigdxgJ6 Some other interesting tidbits: DNS is served by el6/bind, not by AD, but the AD srv records exist and work properly for auto discovery and binding. The samba server...

...the id of the user isn't passed through or looked up correctly > after Kerberos auth, and the user is labelled as a guest user. Guest > users are mapped to bad user in samba config. Here's a bit of logging > when the Windows client tries to access a > share: https://pastebin.com/pbEqj9ZR Actually unknown users (i.e. Bad User) are mapped to the Unix user 'nobody', they probably wouldn't be if you were using an AD DC with the windows clients joined to the domain. The other problem you have here is, sssd has nothing to do with Samba, it is not Samba package, you may get...

...er isn't passed through or looked up correctly >> after Kerberos auth, and the user is labelled as a guest user. Guest >> users are mapped to bad user in samba config. Here's a bit of logging >> when the Windows client tries to access a >> share: https://pastebin.com/pbEqj9ZR > > Actually unknown users (i.e. Bad User) are mapped to the Unix user > 'nobody', they probably wouldn't be if you were using an AD DC with > the windows clients joined to the domain. Whichever user a bad user is being mapped to, I believe this is at the root of the proble...