Re: DirectoryAdmin + FedoraCore1 + openldap-2.1.22-8

No such user means that the SAMBA code can't find the right user,
because it doesn't have the required object class.  It's hard coded to
use the new object class, so it won't find the DA-created users.  The
fix is to fix DA so it supports both the old and the new schemas
simultaneously, and to do this, DA has to check if the Directory server
has one or both of those schemas installed.

Does someone have a patch for DA that fixes this issue?

luck,

El mié, 26-11-2003 a las 16:48, Jesse Keating escribió:
> On Wednesday 26 November 2003 12:59, Jesse Keating wrote:
> > Ah!  That did it, thank you much.  Now, I've hacked the Samba 3.0
> > schema included to provide the historical schema, does anybody know
> > if Samba 3.0 can auth against a historical (samba 2.2) LDAP setup?
> 
> Ok, to further this process, I've rebuild samba on my RHEL box to use 
> ldapsam, and I'm getting this message when trying to use smbclient -L 
> on it:
> 
> Nov 26 13:50:00 kickstation-104 smbd[1330]: [2003/11/26 13:50:00, 0] 
> auth/auth_sam.c:check_sam_security(459)
> Nov 26 13:50:00 kickstation-104 smbd[1330]:   check_sam_security: 
> make_server_info_sam() failed with 'NT_STATUS_NO_SUCH_USER'
> 
> The user exists and all that.  Can anybody help me figure out whats 
> missing?
-- 
	Manuel Amador
	Jefe de I+D
	Amauta
	+593 (9) 847-7372
	GPG key ID: keyserver.net C1033CAD

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/xSi6WyznNMEDPK0RAsMtAJ96rIXh+2MXfWa2SDFgyCrmQbQ63wCeO8Xe
2mFFD3erGMOriotgHVkXKnE=
=r3CQ
-----END PGP SIGNATURE-----