Results 1 to 5 of 5

Thread: ldap 389: port connection refused

  1. #1
    koby is offline Active Member
    Join Date
    Aug 2006
    Posts
    40
    Rep Power
    8

    Thumbs down ldap 389: port connection refused

    Hi, I have in the zimbra server the ldap port 389 opened:

    Code:
    # nmap localhost
    
    PORT    STATE SERVICE
    389/tcp open  ldap
    A telnet in the zimbra server:

    Code:
     # telnet localhost 389
    Trying 127.0.0.1...
    Connected to localhost.localdomain (127.0.0.1).
    But if I try a telnet of another host:

    Code:
    # telnet 192.168.0.90 389
    Trying 192.168.0.90...
    telnet: connect to address 192.168.0.90: Connection refused
    telnet: Unable to connect to remote host: Connection refused
    And the nmap says it's closed:

    Code:
    #nmap 192.168.0.90 -p 389
    
    Interesting ports on 192.168.0.90:
    PORT    STATE  SERVICE
    389/tcp closed ldap
    I want to introduce mail contacts in the ldap server, then my users could see and use these contacts at their address book.

    Any suggestions??

  2. #2
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,480
    Rep Power
    56

    Default

    It should bind to your ip address not localhost. Is your /etc/hosts file correct and your DNS records point to this server?

    What does the following commands give?

    nmap 192.168.0.90
    host `hostname`
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    LDAP Binds to whatever the ldap host is in zmlocalconfig, example:
    It binds to mail.server.com
    so
    telnet mail.sever.com 389

  4. #4
    imarks001's Avatar
    imarks001 is offline Active Member
    Join Date
    May 2006
    Location
    Reston, VA
    Posts
    34
    Rep Power
    9

    Default Iptables or Firewall ?

    Looks like it could be iptables. Run "iptables -nL" and see if ldap is allowed through.

  5. #5
    koby is offline Active Member
    Join Date
    Aug 2006
    Posts
    40
    Rep Power
    8

    Unhappy

    Phoneix in the zimbra server (192.168.0.90) if a run:

    Code:
    nmap 192.168.0.90 -p 389
    
    PORT    STATE  SERVICE
    389/tcp closed ldap
    and
    Code:
    host localhost 
    
    localhost has address 127.0.0.1
    localhost has IPv6 address ::1
    I bought a domain (name ex: domain.com) but the installation of the zimbra server was with the domain name localhost.localdomain and the HELO don't like that. With gmail,hotmail all works good but with others think that my mails are spam.

    My domain "domain.com" has a mx record to a publid ip adress (to the router) then the router it's configured to forward the port 25 to my zimbra server (192.168.0.90) and the zimbra server has this /etc/hosts:

    127.0.0.1 localhost.localdomain localhost
    192.168.0.90 mail.example mail

    Note:I know the zimbra server's name "localhost.localdomain" it's wrong but when I installed zimbra every name I try had errors (DNS can't resolve it). Then I followed the steps of a how-to run BIND (posted here ) in the zimbra server. Then my bind config file look like this:

    Code:
    $ttl 38400
    @       IN      SOA     mail.okkum. root.mail.okkum. (
                            2005110200
                            10800
                            3600
                            604800
                            38400 )
    @             IN        NS      mail.okkum.
    @             IN        MX     10 192.168.0.90
    @             IN        A       192.168.0.90
    mail.okkum IN        A       192.168.0.90
    #mail1       IN       CNAME     mail
    #mail2       IN        CNAME     mail
    But I got the same errors. (DNS can't resolve it) Then I modified the BIND file to this:

    Code:
                    IN NS           localhost
    localhost       IN A            127.0.0.1
    localhost       IN MX   10              localhost
    Then I added in the zimbrawebadmin the domain I bought "domain.com" and all "worked good", but now I'm seeing that I have a BIG problem with the spam by the localhost.localdomain name.
    And the ldap service.
    Last edited by koby; 09-07-2006 at 01:08 AM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. initializing ldap...FAILED(256)ERROR
    By manjunath in forum Installation
    Replies: 39
    Last Post: 06-07-2013, 10:27 AM
  2. 3 testing: LDAP: 389 Failed when restore zimbra
    By victorLeong in forum Administrators
    Replies: 15
    Last Post: 05-24-2007, 06:45 AM
  3. Post instsallation problems
    By Assaf in forum Installation
    Replies: 14
    Last Post: 01-29-2007, 11:38 AM
  4. Error on openSUSE 10.1
    By piti in forum Installation
    Replies: 7
    Last Post: 11-07-2006, 01:21 PM
  5. Is it started or not
    By kwelipatton in forum Installation
    Replies: 10
    Last Post: 03-28-2006, 11:11 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •