ON: SuSE 9.1, didn't use the included RPM files due to force of habit mainly Computer: P4 (1.5) on a crufty Intel i845 mobo requiring a 1.5v AGP vidcard DID: configure --with-smbwrapper-yes --with-ads=yes --with-automount=yes --with-smbmount=yes --with-pam=yes --with pam_smbpass=yes --with-winbind=yes (note: I'm sure some of these could have been omitted, but it normally Just Works, so that's how I've been doing my configures) Configure script had to be run a couple of times as it did correctly catch some missing deps. Eventually, script ran, samba was compiled, life appeared good. But winbind wasn't working right - it'd start but wbinfo -u or -g threw a couldn't connect error. A quick look in /var/log/messages turned up this info: May 19 14:16:11 workstation kdm: :0[3579]: PAM adding faulty module: /lib/security/pam_krb5.so workstation:~ # cat /var/log/messages | grep krb5 May 19 14:16:11 workstation kdm: :0[3579]: PAM unable to dlopen(/lib/security/pam_krb5.so) May 19 14:16:11 workstation kdm: :0[3579]: PAM [dlerror: /lib/security/pam_krb5.so: cannot open shared object file: No such file or directory] Aha! I installed the pam_krb5 rpm and suddenly all was well =] I guess this isn't exactly a show-stopper, but it'll probably reduce the support burden to catch this missing dep at configure time. Cheers, Mike Ely Computer Support Specialist Phoenix-Talent School District #4 Phoenix, OR, USA
Forgot to mention - I'm using the MIT Kerberos (1.3.3) from their binary distribution. Again, force of habit - SuSE likes Heimdal but had more trouble getting that kerb to work.
This is a pam_krb5 issue and has nothing to do with Samba or winbindd. Sorry.
database cleanup