[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: port 389 not present while slapd is running

To: "nugulus@netscape.net" <nugulus@netscape.net>
Subject: Re: port 389 not present while slapd is running
From: matthew sporleder <msporleder@gmail.com>
Date: Thu, 11 Aug 2005 09:08:32 -0400
Cc: openldap-software@OpenLDAP.org
Content-disposition: inline
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kAw3h6RozaGjbaa802mQlMW+3XXLX8obBDkef+Supzx3RUsfxdB54WyYw1gXdLhp9kuNyW5XTqULf/y6lScMlxv/VDk4MyRhJ6h3stmBT1s//yLpexILowzpB0PzBaM229zNgz8ioSaeNoxjWNOaMV5MbZykjPE+0j8nEJCTVVk=
In-reply-to: <6AB87B63.25E95848.00210FF7@netscape.net>
References: <6AB87B63.25E95848.00210FF7@netscape.net>

The listen port is configurable.  I tend to use the -h ldap:// command
line, but check out your own configs.  Also look into the lsof command
to search for what sockets your pid has opened.

On 8/7/05, nugulus@netscape.net <nugulus@netscape.net> wrote:
> ldapsearch -x
> will get "ldap_bind: Can't contact LDAP server (-1)".
> 389 is not in the output of "nmap localhost".
> "telnet localhost 389" got refused.
>

References:
- port 389 not present while slapd is running
  - From: nugulus@netscape.net

Prev by Date: Re: ldapsearch wrapping at 76 chars
Next by Date: Re: port 389 not present while slapd is running
Index(es):
- Chronological
- Thread