--On Tuesday, October 31, 2006 8:47 AM +0100 Dieter Kluenter dieter@dkluenter.de wrote:
Rob Tanner rtanner@linfield.edu writes:
A ps command confirms that the start-up script did the right thing:
/usr/local/libexec/slapd -u ldap -h ldap:/// ldaps:///
But ssl connections fail and a netstat command only shows the server listening on port 389.
Is there something I'm missing at this point merely to get the server listening on port 636?
The examples in man slapd(8) show the URLlist quoted
-h "ldap:/// ldaps:///"
And you may want to understand the difference between TLS over port 389 and SSL over port 636.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html