Hi All I've compiled Samba 3.0 alpha 17 using --with-ldapsam. In smb.conf I've got: passdb backend = ldapsam ldap admin dn = "cn=Manager,o=Sambatest,c=AU" ldap suffix = c=AU ldap ssl = off ... and the admin dn password is in the secrets.tdb file. Whenever I try to connect to samba, I get the following error message: [2002/05/28 09:34:07, 5] passdb/pdb_interface.c:make_pdb_context_name(203) Attempting to find an passdb backend to match ldapsam (ldapsam) [2002/05/28 09:34:07, 5] passdb/pdb_interface.c:make_pdb_context_name(208) Found pdb backend ldapsam (at pos 4) [2002/05/28 09:34:07, 0] passdb/pdb_interface.c:make_pdb_context_name(213) pdb backend ldapsam did not correctly init (error was NT_STATUS_INVALID_PARAMETER) [2002/05/28 09:34:07, 0] passdb/pdb_interface.c:make_pdb_context_name(221) failed to select passdb backed! Other than missing an "n" in "backend", :), is there anything clearly wrong with my setup? Am I missing a configuration directive in smb.conf? I've had Samba 2.2.x working with LDAP but I guess things have changed in 3.0. Thanks in advance for any help. Regards, Gonzalo.
On Tue, May 28, 2002 at 10:09:12AM +1000, Gonzalo Servat wrote:> Hi All > > I've compiled Samba 3.0 alpha 17 using --with-ldapsam. In smb.conf I've > got: > > passdb backend = ldapsam > ldap admin dn = "cn=Manager,o=Sambatest,c=AU" > ldap suffix = c=AU > ldap ssl = off > > ... and the admin dn password is in the secrets.tdb file. > > Other than missing an "n" in "backend", :), is there anything clearly > wrong with my setup? Am I missing a configuration directive in smb.conf?You need to set that to 'passdb backend= ldapsam:ladp://ldap.server:port> I've had Samba 2.2.x working with LDAP but I guess things have changed > in 3.0.Yes, I have changed a few things. We may change them again - if I can come up with a better way to express this stuff. Andrew Bartlett
Andrew, I just wanted to let you know that I managed to get the Win2k box to join the domain & login successfully. The last problem I emailed you about before ("Access is denied") remains. Samba fails to automagically create a computer account if it doesn't exist, however, if you create it manually then it gets past that error. I got a new error after that which was "There is no user session key for the specified logon session" and I fixed that by adding 'use spnego no'. Just thought I'd let you know incase anyone else asks the same questions I did. Thanks again! Regards, Gonzalo. On Wed, 2002-05-29 at 16:36, abartlet@samba.org wrote:> On Wed, May 29, 2002 at 03:51:30PM +1000, Gonzalo Servat wrote: > > > > Would you like me to supply some debugging info ? > > > > Not really, I'm a bit busy and this does look like a configuration error. > > Andrew Bartlett
On Wed, May 29, 2002 at 05:00:44PM +1000, Gonzalo Servat wrote:> Sorry Andrew to hassle you again. > > Just one more question. I noticed in the logs that it checks to see if > computername$ exists, and if it doesn't it tries to add it. The error > message is: > > "NO user RID specified on account apollo$, cannot store!"You either need to use ldapsam_nua or setup an 'add machine script' (both of these are HEAD only options) The _nua backend allows accounts to be added to LDAP without an already allocated unix user (and therfore RID). Andrew Bartlett