Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: Good Old LDAP

  1. #21
    agnOstos is offline Loyal Member
    Join Date
    Oct 2005
    Posts
    96
    Rep Power
    9

    Default

    Good news! downloading of updates seems to have stalled.

  2. #22
    rsharpe is offline Elite Member & Volunteer
    Join Date
    Nov 2005
    Location
    London, ON
    Posts
    255
    Rep Power
    9

    Default Brand New FC4

    I'm at this menu and it is telling me that it can connect to my LDAP server.
    I have two separate server my MTA and my Mailstore/LDAP. My Mailstore is running just fine, but when I try to install I get to the menu and it says LDAP server and LDAP password unset, so I set them and it tells me it has failed. I can telnet to 389 on the LDAP server. I also did a tcpdump on the "to be" MTA and it wasn't even trying to send any packets at all, it ever even attempted it. And on another oddity if I change the LDAP hostname to the local hostname, it doesn't argue or anything. I have done a netstat there are no LDAP servers running, it is a minimal install, and I have also done a yum update, and reboot.

  3. #23
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default ldap logic

    If you're installing, and you've set ldap to the localhost, and it's not running, I don't try to connect to it.

    If you've set it to a remote host, I do try to connect to it, since I can't very well start it from the installer.

    So - if you've set it to a remote server, done a tcpdump, and verified that there are no packets sent to it, then it's probably a DNS resolution issue. What do you get from:
    host ?

  4. #24
    rsharpe is offline Elite Member & Volunteer
    Join Date
    Nov 2005
    Location
    London, ON
    Posts
    255
    Rep Power
    9

    Default

    Well.... I thought it might be DNS to, but in the tcpdump there wasn't even a DNS packet for resolution. I also put an entry into the host table. I could also telnet to port 389 using the hostname. I have also tried to put the IP address into the Main Menu, it still failed. Now I'm not sure if this would affect anything, it really shouldn't but, I'm trialing this on VMware ESX server, and I'm 99% sure that this shouldn't be a problem.

    Tomorrow I will verify that this isn't a DNS problem.

  5. #25
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default /etc/hosts and DNS are orthogonal

    Just because it's in /etc/hosts, doesn't mean that you'll get to it if a server is using a DNS lookup.

    If you put the IP addr into the menu, it should succeed - you can get to port 389 via IP, I assume?

    Of course, it may not be connection - it could be auth that's failing - did you set the LDAP password on the MTA to be? It has to match the ldap password on the ldap server.

Page 3 of 3 FirstFirst 123

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. LDAP Replication Experiences
    By technikolor in forum Administrators
    Replies: 4
    Last Post: 11-12-2008, 12:52 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. Mac OSX install: Java errors & LDAP CA error
    By jefbear in forum Installation
    Replies: 9
    Last Post: 12-16-2006, 03:39 PM
  4. Replies: 4
    Last Post: 11-15-2006, 12:16 PM
  5. Replies: 2
    Last Post: 05-24-2006, 10:01 AM

Posting Permissions

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