search for: 07.209878

So this got me thinking that maybe a chunk of my problem is with LDAP itself on the server. Executing "slapcat" shows me what I believe to be the correct content, including what looks like appropriate content underneath the following: dn: sambaDomainName=DRBHOME,dc=drbhome,dc=ca That seems to answer the question about whether the domain info is actually there. >> Can you also

On 19/02/16 01:53, Dave Beach wrote: > So this got me thinking that maybe a chunk of my problem is with LDAP itself on the server. Executing "slapcat" shows me what I believe to be the correct content, including what looks like appropriate content underneath the following: > > dn: sambaDomainName=DRBHOME,dc=drbhome,dc=ca > > That seems to answer the question about whether

> Is ldap running on the Samba machine ? Yes, this is the only server in the domain. > Have you set the ldap password with 'smbpasswd -w' Yes, and based on log.smbd Samba can connect . > I would remove this line: server role = standalone server You are not running a standalone server. The parameter is new since the previous version of Samba I was running (v3.5.6), and

Hi Rowland, hi Dave On 11:51:17 wrote Rowland penny: > On 19/02/16 01:53, Dave Beach wrote: > > So this got me thinking that maybe a chunk of my problem is with > > LDAP itself on the server. Yes, you are right. But it is really only a piece of the problem. You are comming from the 3.5 version of samba. Early in 3.6 some things have changed. > > Executing