-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Jim C. - -- - ----------------------------------------------------------------- | I can be reached on the following Instant Messenger services: | |---------------------------------------------------------------| | MSN: j_c_llings @ hotmail.com AIM: WyteLi0n ICQ: 123291844 | |---------------------------------------------------------------| | Y!: j_c_llings Jabber: jcllings @ njs.netlab.cz | - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwTUA57L0B7uXm9oRApk/AJ4jli1ZX+T93+4L8LSg61HAN33+gACfXZJX TomDrFYSkmJPsYzL8fHVbHo=btwE -----END PGP SIGNATURE-----
Jim C. wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Did ldap machine suffix ever get fixed so that it can be in a sperate > container from ldap user suffix?Is there any problem to be fix on samba side? I've been using separate container for machine without any problem ( almost 8 months now) -- --beast
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK, so what I am hearing is that: 1. It is still a problem. 2. But it isn't a Samba problem, it is an nss_ldap problem. 3. There might be some work arounds. Possible workarounds: A. Burry the Two OU's one deeper and do a subtree search on the parent OU. Works but not scaleable. B. Add "filter" keyword to uh... Is it /etc/ldap.conf or nss_switch.conf? Syntax? Am I in the right ballpark here? :-) Jim C. - -- - ----------------------------------------------------------------- | I can be reached on the following Instant Messenger services: | |---------------------------------------------------------------| | MSN: j_c_llings @ hotmail.com AIM: WyteLi0n ICQ: 123291844 | |---------------------------------------------------------------| | Y!: j_c_llings Jabber: jcllings @ njs.netlab.cz | - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwoPU57L0B7uXm9oRAvFRAJ49HG+hh+tVITu09dPBqRyPvGmOzQCeL7Xy 2JbBI6+wWIlLhJrp+QxRgAs=2WmN -----END PGP SIGNATURE-----