[Samba] FreeBSD 8.1 & Samba4 alpha11 domain controller - cldapd bind problem

Daniel Müller mueller at tropenklinik.de
Fri Nov 12 01:34:03 MST 2010

Did you bind to an interface? Interfaces= xxx.xxx.xxx.xxx
Is your dns server running and pointing to the samba ads?
What about the firewall?

EDV Daniel Müller

Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 Tübingen

Tel.: 07071/206-463, Fax: 07071/206-499
eMail: mueller at tropenklinik.de
Internet: www.tropenklinik.de

-----Ursprüngliche Nachricht-----
Von: jelle.p at sthuma.nl [mailto:jelle.p at sthuma.nl] Im Auftrag von Oeboema
Gesendet: Freitag, 12. November 2010 09:11
An: mueller at tropenklinik.de
Cc: Michael Wood; samba at lists.samba.org; samba-technical at lists.samba.org
Betreff: Re: [Samba] FreeBSD 8.1 & Samba4 alpha11 domain controller - cldapd
bind problem

> Did you made a testparm -vv|grep cldap, then press enter
> You may see this:
> server services = smb, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind,
> ntp_signd, kcc, dnsupdate
>        cldap port = 389
> First of all server services must point to cldap
> And the cldap port.
> If you have another service running on the same port it will not work(ex.:
> openldap does the same port)

Thanks for the tip but I get exactly the same "grep" output; all
server services are pointing to port 389.

I've built a couple of "fresh" systems in order to test this Samba
installation so besides SSH nothing is listening yet on any other port
besides 22 and no firewall running. Maybe I should use OpenLDAP as an
alternative backend for Samba but after some quick googling I've been
reading a lot of reports that OpenLDAP no longer supports UDP......

More information about the samba mailing list