Ok, I went back and compiled without ldapsam_compat. I am now trying to simply use ldapsam. However, I get this error in the log.smbd when trying to connect with a client:
[2004/12/23 12:59:18, 0] passdb/pdb_interface.c:make_pdb_methods_name(664) No builtin nor plugin backend for ldapsam found [2004/12/23 12:59:18, 1] passdb/pdb_interface.c:make_pdb_context_list(765) Loading ldapsam:ldap://lincon.beloit.edu failed! [2004/12/23 12:59:21, 0] passdb/pdb_interface.c:make_pdb_methods_name(664) No builtin nor plugin backend for ldapsam found [2004/12/23 12:59:21, 1] passdb/pdb_interface.c:make_pdb_context_list(765) Loading ldapsam:ldap://lincon.beloit.edu failed!
Here is the Global part of my smb.conf file:
[global]
encrypt passwords = yes
passdb backend = ldapsam:"ldap://lincon.beloit.edu";
dns proxy = no
log file = /var/log/samba/%m.log
load printers = no
printing =
server string = backt.beloit.edu
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
workgroup = its
os level = 20
hosts allow = all localhost
printcap name =
max log size = 50
max disk size = 100
invalid users = root
ldap suffix = ou=People,dc=lincon,dc=beloit,dc=edu
ldap admin dn = cn=admin,dc=lincon,dc=beloit,dc=edu
ldap ssl = noDo I need additional or different ldap options in this file? Note that we do NOT use Windows Domains. I have no desire to do anything with Windows Domains. There are no Windows servers or workstations with accounts for global access. We are very Unix based here.
I guess I am not understanding whether this is a problem with the ldap server or the samba server at this point. I see that some people use the ldap machine variable in smb.conf. Since I don't care about Windows Domains, do I still need that variable?
Tim
Tim Tyler írta:
Samba Ldap experts,
I am trying to recompile samba to support ldap. After compiling samba with --with-ldapsam, I had no errors with configure or compilation. However, after starting up smbd and nmbd, I get these errors in the log.smbd file when I try to connect to the server:
[2004/12/20 13:57:02, 0] lib/debug.c:reopen_logs(590)
Unable to open new log file /var/log/samba/smbd.log: No such file or directory
[2004/12/20 13:57:02, 0] passdb/pdb_interface.c:make_pdb_methods_name(664)
No builtin nor plugin backend for ldapsam found
[2004/12/20 13:57:02, 1] passdb/pdb_interface.c:make_pdb_context_list(765)
Loading ldapsam:ldap://lincon.beloit.edu failed!
[2004/12/20 13:57:05, 0] passdb/pdb_interface.c:make_pdb_methods_name(664)
No builtin nor plugin backend for ldapsam found
[2004/12/20 13:57:05, 1] passdb/pdb_interface.c:make_pdb_context_list(765)
Loading ldapsam:ldap://lincon.beloit.edu failed!
Is this a problem on the samba side or the ldap server side which is on another server? Any hints about resolving it?
I am just not sure where to begin to look.
Tim Tyler Network Engineer - Beloit College [EMAIL PROTECTED]
If you are trying to compile samba3.0.x, then you don't need to pass any special configure option for ldapsam support. The --with-ldapsam configure option is for enabling the ldapsam_compat passdb backend, whith which you could use your old (samba2) ldap user database, until you convert it for using the newer (samba3) schema. I would recommend against using the ldapsam_compat passdb backend, as it there only for compatibility, and is not well tested.
Cheers,
Geza
Tim Tyler
Network Engineer - Beloit College
[EMAIL PROTECTED]
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
