I don't understand what's happening then. I copied and loaded the schema, added objectclass SambaSamAccount and sambaSID that matches uidNumber.
when I do smbpasswd -a user, to populate ldap with windows passwords, I get complaints that userdn.... "has unknown object class "sambaAccount". if I look at the error log file on the ldap server, it also shows modifications attempts with non-existing objectclass sambaAccount, but why isn't it using sambaSamAccount ?? I compiled without ldapsam, even tried explicitly using --without-ldapsam. /usr/local/samba/sbin/smbd --version Version 3.0.21c CC=cc CPPFLAGS="-I/usr/local/include -I/usr/local/ssl/include" LDFLAGS="-L/usr/local/lib-L/usr/local/ssl/lib -R/usr/local/lib -R/usr/local/ssl/lib" ./configure --with-ldap --with-pam --with-ads --with-krb5=/usr/local/ --with-smbwrapper > On Tue, 2006-03-21 at 14:13 -0500, [EMAIL PROTECTED] wrote: >> In netscape5x directory schema, the object class is defined as >> SambaSamAccount account, instead of the usual SambaAccount that Samba >> uses >> for all its ldap binds. How can I change this behavior on Samba's side ? > > sambaSamAccount is the Samba 3.0 schema. Samba 2.2 used sambaAccount. > > Andrew Bartlett > > -- > Andrew Bartlett http://samba.org/~abartlet/ > Authentication Developer, Samba Team http://samba.org > Student Network Administrator, Hawker College http://hawkerc.net > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba