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

389 port is closed from the client point of view



Hello,

I am trying to get my ldap binding running, but some how it doen't work!
When I checked the port using nmap, I can see clearly that it is closed while the server listens to it!

client# nmap -p 389 ldap.domain.com

Starting Nmap 5.00 ( http://nmap.org ) at 2013-01-29 23:09 EST
Interesting ports on  ldap.domain.com (203.28.247.83):
PORT    STATE  SERVICE
389/tcp closed ldap

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds


root@server:/etc/ldap# nmap -p 389 localhost

Starting Nmap 5.00 ( http://nmap.org ) at 2013-01-29 23:09 EST
Interesting ports on localhost (127.0.0.1):
PORT    STATE SERVICE
389/tcp open  ldap

Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
root@server:/etc/ldap#
root@server:/etc/ldap# nmap localhost

Starting Nmap 5.00 ( http://nmap.org ) at 2013-01-29 23:10 EST
Interesting ports on localhost (127.0.0.1):
Not shown: 994 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
389/tcp open  ldap
464/tcp open  kpasswd5
636/tcp open  ldapssl
749/tcp open  kerberos-adm

Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds
root@server:/etc/ldap# cat /etc/hosts
127.0.0.1 localhost
#127.0.1.1 ldap.domain.com ldap
203.28.247.83 ldap.domain.com        ldap

How can I fix this?

Thanks.