[Samba] ldapsam_compat backend hosed in v3.0.2

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Graham Leggett wrote:
| Hi all,
|
| In an attempt to get the old v2.2 Samba behaviour to work, I
| tried to  enable the ldapsam_compat mode in passwd backend.
|
| Win2k cannot connect, username and password not accepted.
|
| The LDAP logs reveal that Samba is trying to make the
| following search:
|
| (&(&(uid=minfrin)(objectClass=sambaSamAccount))(objectClass=sambaAccount))
|
| This search returns users who have both the old v2.2
| objectclass _and_  the new v3.0 objectclass at the same time,
| which is nobody if standard  tools for editing v2.2 LDAP
| entries are used.

Do you have 'ldap filter' set ?  Best not to.  Also, please
check the level 10 Samba debug logs and see the surrounding
conditions with this search>  That would be helpful to know.





cheers, jerry
- ----------------------------------------------------------------------
Hewlett-Packard            ------------------------- http://www.hp.com
SAMBA Team                 ---------------------- http://www.samba.org
GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
"If we're adding to the noise, turn off this song" --Switchfoot (2003)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAUGG+IR7qMdg1EfYRAniFAKCmZ9zJpDWYZwxiY2llWkv/xW72FgCgpYWC
aj3hmxvQajiOjsrReNLQv4M=
=vzQs
-----END PGP SIGNATURE-----