... /etc/services only maps port numbers to service names. Try: netstat -an | grep 389 or even: netstat -anp | grep 389 to see what is actually in use. I would
Message 1 of 2
, May 24, 2010
On 24May2010 13:00, Dan <hyattdj@...> wrote:
| I am trying to configure a 389 directory server for proof of concept....setup-ds-admin.pl
| after configuring the server, the application tests it
| and I get:
| The server 'ldap://sdrac0104.frxntnyc.frx2.com:389/o=NetscapeRoot' is not reachable. Error: unknown error
| Please try again, in case you mis-typed something.
| Configuration directory server URL [ldap://sdrac0104.frxntnyc.frx2.com:389/o=NetscapeRoot]:
| vi /etc/services
| ports 389 are open UDP and TCP
| ulistproc 372/udp ulistserv
| ldap 389/tcp
| ldap 389/udp
| svrloc 427/tcp
/etc/services only maps port numbers to service names.
netstat -an | grep 389
netstat -anp | grep 389
to see what is actually in use.
I would guess the LDAP server damon is not actually running.
When buying and selling are controlled by legislation, the first things
bought and sold are the legislators. - P.J. O'Rourke
Your message has been successfully submitted and would be delivered to recipients shortly.
Changes have not been saved
Press OK to abandon changes or Cancel to continue editing
Your browser is not supported
Kindly note that Groups does not support 7.0 or earlier versions of Internet Explorer.
We recommend upgrading to the latest Internet Explorer, Google Chrome, or Firefox. If you are using IE 9 or later, make sure you turn off Compatibility View.