See at #987 bug.
There is a workarround :
The work arround is to configure nssldap user suffix to a suffix
containing both
users and machines entries in its scope (but it's not very usefull...).
Ex : you have people in ou=users,dc=toto,dc=com
and machines in ou=computers,dc=toto,dc=com
And the
Hi everybody,
why in the new 3.0.3/4 when a new windows machine join on domain
samba search (in ldap backend) on ou=Users and not in ou=computers?
my smb.conf:
ldap passwd sync = Yes
ldap admin dn = cn=ldap manager,dc=intra,dc=local
ldap suffix = dc=intra,dc=local
This is a known problem. The developers have only commented that you
should use the same container for machines as for people in samba 3.0.x
thus far. I have filed this as bug #1292, but thus far there has been no
official word on a fix.
https://bugzilla.samba.org/show_bug.cgi?id=1292
Cheers
I have tried samba 3.0.1pre2 on suse 8.2. I force to keep Computer and
User account in single tree People. I don't know it fixed.
eg.
User account:
uid=testuser,ou=People,dc=sfgroup,dc=com
Machine acount:
uid=sales$,ou=People,dc=sfgroup,dc=com
SR
Recently I've read here, that there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody,
Recently I've read here, that there is a problem with storing computer
accounts in a separate container, of LDAPSAM backend.
We're successfully using Samba3.0.1pre1 (with a patch for bug#64, #532
and #569, Win9x userlist problem)
with
Recently I've read here, that there is a problem with storing computer
accounts in a separate container, of LDAPSAM backend.
We're successfully using Samba3.0.1pre1 (with a patch for bug#64, #532
and #569, Win9x userlist problem)
with separate ous for users and computers, after configuring
