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 user suffix in nssldap configuration set up to : dc=toto,dc=com With that, you can have in your smb.conf : ldap user suffix = ou=Users ldap machine suffix = ou=Computers Yohann F. users and machines entries in its scope (but it's not very usefull...). Le mar 11/05/2004 � 22:10, Ross Becker a �crit : > 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 > Ross Becker > Francesco Defilippo wrote: > > > 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 > > ldap group suffix = ou=Groups > > ldap user suffix = ou=Users > > ldap machine suffix = ou=Computers > > ldap idmap suffix = ou=Users > > > > > > > > > > > > SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497 > > -- Yohann F. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
