When trying to register a new samba server with a LDAP directory (happens automatically on startup of smbd) it tries to add the new host directly to the directory suffix instead of to the machine suffix. I first encountered this bug in RHEL4.5. I downloaded and checked for the same bug in samba-3.0.25b-1.el4_6.4 as well. Bug exists also in the latest (vanila) samba-3.0.28.
Are referring to the sambaDomain object ? Can you provide logs, ldifs or any other indication of the problem?
Hi, I'm referring to the "sambaDomainName" object. Following is a LDIF of the object created by smbd *after* my patch. Before my patch smbd tried to create the object directly under dc=test (and not under ou=SambaHosts,dc=test) dn: sambaDomainName=RHEL4-U4-ES,ou=SambaHosts,dc=test sambaDomainName: RHEL4-U4-ES sambaSID: S-1-5-21-1884737327-3722201558-1353666255 sambaAlgorithmicRidBase: 1000 objectClass: sambaDomain sambaNextUserRid: 1000 My smbd.conf configuration looks like this: [global] workgroup = MYGROUP server string = Samba Server passdb backend = ldapsam:"ldap://192.168.20.113:389" log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = /etc/printcap dns proxy = No ldap admin dn = cn=root,dc=test ldap machine suffix = ou=SambaHosts ldap suffix = dc=test ldap user suffix = ou=People idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 cups options = raw [homes] comment = Home Directories read only = No browseable = No
For various technical reasons, that LDAP object needs to exist at the top-level suffix you defined via "ldap suffix". As already pointed out at https://bugzilla.samba.org/show_bug.cgi?id=5233 we can't easily change this. Sorry.