Edgar,
My opinion is that pam_unix should be tried before pam_winbind. Sending
your root password to Active Directory is Not a good idea.
The same applies to pam-krb5 if it does that.
--
Winbind package does not provide PAM configuration
https://bugs.launchpad.net/bugs/282751
You received this
The ones of you having this issue: Are you by chance using the SFU
idmap? I've isolated my problem down to that I believe.
If not, see if you can grab the stack trace. The samba panic action
should put it in the log files.
--
winbind forgets uid/name gid/name mappings in regulary periods
https:
Public bug reported:
Binary package hint: samba
When using Winbind to provide user NSS information, restarting Winbind
for any long period can cause Very Bad Things. The current desktop
session will for instance not be able to find $HOME, nor even it's own
user name. Applications break. Browsers
