20 Nov
2014
20 Nov
'14
1:03 a.m.
On Wed, Nov 19, 2014 at 04:09:32PM -0500, Jason Swank wrote:
What about the interface bind conflict when ldap:// is specified? Is that expected behavior?
Yes. ldap:/// binds to port 389 on *all* IPv4 and IPv6 interfaces. If you also have ldap://<hostname>/ then you are trying to bind at least one of those interfaces twice.
Note also that you should be using fully-qualified domain names everywhere. Simple hostnames will not work properly with TLS.
Andrew
--
-----------------------------------------------------------------------
| From Andrew Findlay, Skills 1st Ltd |
| Consultant in large-scale systems, networks, and directory services |
| http://www.skills-1st.co.uk/ +44 1628 782565 |
-----------------------------------------------------------------------