AW: Slapd listens only on 636

["Zamangoer, Ferruh" <ferruh.zamangoer@materna.de>]

Thanks I have only show for the port 636 informer times .
I have not see in /etc/services that ldap on port 389 for tcp was disabeld.

Soory that i have not look before I posted the message  

#ldap            389/tcp                 # Lightweight Directory Access
Protocol
ldap            389/udp                 # Lightweight Directory Access
Protocol


Thanks Darren 

-----Ursprüngliche Nachricht-----
Von: Darren Gamble [mailto:Darren.Gamble@sjrb.ca]
Gesendet: Donnerstag, 28. März 2002 16:25
An: Zamangoer, Ferruh; 'openldap-software@OpenLDAP.org'
Betreff: RE: Slapd listens only on 636


Good day,

Well, that's obliviously not the problem, then. =/

Sorry, I'm not sure what else to suggest.  I presume you've checked your
/etc/services file and tried to connect to the service regardless.

Perhaps someone more experienced could help?

============================
Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948


-----Original Message-----
From: Zamangoer, Ferruh [mailto:ferruh.zamangoer@materna.de]
Sent: Thursday, March 28, 2002 8:24 AM
To: 'Darren Gamble'; 'openldap-software@OpenLDAP.org'
Subject: AW: Slapd listens only on 636


When I start my server I see following output:


solo:/usr/local/libexec # /usr/local/libexec/sslslapd
@(#) $OpenLDAP: slapd 2.0.23-Release (Thu Mar 14 12:42:21 CET 2002) $
        root@solo:/tmp/openldap-2.0.23/servers/slapd
daemon_init: listen on ldap://139.2.145.38:389/
daemon_init: listen on ldaps://139.2.145.38:636/
daemon_init: 2 listeners to open...
ldap_url_parse_ext(ldap://139.2.145.38:389/)
daemon: initialized ldap://139.2.145.38:389/
ldap_url_parse_ext(ldaps://139.2.145.38:636/)
daemon: initialized ldaps://139.2.145.38:636/
daemon_init: 2 listeners opened
slapd init: initiated server.
slap_sasl_init: initialized!
slapd startup: initiated.
slapd starting


nevertheless I see only when I use the command: 

tcp        0      0 solo.materna-ffm.:ldaps *:*                     LISTEN

:( 



-----Ursprüngliche Nachricht-----
Von: Darren Gamble [mailto:Darren.Gamble@sjrb.ca]
Gesendet: Donnerstag, 28. März 2002 16:14
An: Zamangoer, Ferruh; openldap-software@OpenLDAP.org
Betreff: RE: Slapd listens only on 636


Good day,

I haven't used this particular option, but, I think the URL's need to have a
trailing slash (i.e. ldap://xxx.xxx.xxx.xxx:389/)

It maybe that there is something in the code that adds the trailing / to the
entire string if one is missing, which is why you get the one listening but
not the other.

Of course, you should check the log for errors.  What does the log say?

Try this out, anyway.

============================
Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948


-----Original Message-----
From: Zamangoer, Ferruh [mailto:ferruh.zamangoer@materna.de]
Sent: Thursday, March 28, 2002 8:09 AM
To: openldap-software@OpenLDAP.org; 'openssl-users@openssl.org'
Subject: Slapd listens only on 636


Hi all,

I have started the slapd with the following command: 

slapd -d 1 -h "ldap://xxx.xxx.xxx.xxx:389 ldaps://xxx.xxx.xxx.xxx:636"

when i use the following command:

netstat -a | grep -i ldap

I become the following output 

tcp        0      0 solo.materna-ffm.:ldaps *:*                     LISTEN


Must be there not two listeners, one of them, must listen on port 389 and
the another on 636 .


Thanks for your help in advance

:) 

Regards Ferruh