Can't bind to zimbra's ldap, port seems to be closed

[penguinknight]

I am following the guide
UNIX and Windows Accounts in Zimbra LDAP and Zimbra Admin UI - ZimbraWiki
and I have had a working samba server up and I get cannot bind, cannot contact LDAP server errors in log.smbd

When I run
nmap -sT -O email

I get
Not shown: 1689 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
110/tcp open pop3
143/tcp open imap
465/tcp open smtps
993/tcp open imaps
995/tcp open pop3s

Which shows that nothing is listening on 389

All ports should be accepting by default so I guess just nothing is listening.

Any help would be appreciated

Info:
Zimbra 4.5.5 Open Source
Ubuntu 6.10, updated before install of ZCS
New install
Samba server was a ubuntu 6.10 Virtual machine (that could communicate with the host on every other port so it's not a limitation of the VMware networking.

Let me know if any other information would help.

Thanks

[phoenix]

Is there anything in the logs indicating why LDAP hasn't started? Have you tried the troubleshooting tips from the wiki?

[penguinknight]

There are only two additional entries in the log file when starting it from a stopped state. I ran the command grep slapd /var/log/syslog as advised from another site to get the slapd log.

May 28 00:34:35 email slapd[26229]: @(#) $OpenLDAP: slapd 2.3.34 (Apr 2 2007 10:28:20) $ ^Iroot@build-ubuntu:/home/build/p4/main/ThirdParty/openldap/openldap-2.3.34/servers/slapd
May 28 00:34:35 email slapd[26230]: slapd starting

And zimbra works just fine. The only part of LDAP that isn't working is accessing it from another machine on the network.

And yes, I checked the wiki briefly but will have another look.

Thanks!

UPDATE: Whoops! I should have clicked first, you sent me directly to what I needed to read! Thank you

I still don't have it fixed but this tells me that is should be listening to my hostname :-/
zimbra 26230 0.0 0.7 17992 4024 ? Ssl 00:34 0:00 /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://email.domain.com:389 -f /opt/zimbra/conf/slapd.conf
zimbra 27660 0.0 0.1 1664 516 pts/0 S+ 00:40 0:00 grep slapd

output of hostname:
email
output of hostname -f:
email.domain.com

[penguinknight]

Figured it out (that's to that wonderful link, thank you) but haven't fixed it

sudo /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://email.domain.com:389 -f /opt/zimbra/conf/slapd.conf

the domain name being there, or anything being there, actually causes a problem with listening.
I removed it and manually launched it...so for now I'm just not going to restart my server.

in /opt/zimbra/bin/ldap there is the command that is ran but it includes a variable $my_url ...should I just remove the variable and hard-code that part of the file with what I need to be running?

Is there is nicer way of doing this?

Thanks!

[phoenix]

As mentioned in the wiki, the usual reason for LDAP problems is resolving DNS to the hostname. Are your DNS records correct? What does the following return:

host `hostname` - backticks not quotes
dig yourdomain.com any

[penguinknight]

Ah, I had tried
host ldap-hostname
which produced it's IP, 10.107.8.30
dig seems to say the same and the server queried is my router at 10.107.8.1 which holds a single A record for it as it doesn't have MX capabilities in the web interface (and it doesn't hurt anything as far as I can tell).

dig email.domain.com any

; <<>> DiG 9.3.4 <<>> email.domain.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61632
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;email.domain.com. IN ANY

;; ANSWER SECTION:
email.domain.com. 0 IN A 10.107.8.30

;; Query time: 1 msec
;; SERVER: 10.107.8.1#53(10.107.8.1)
;; WHEN: Mon May 28 02:29:08 2007
;; MSG SIZE rcvd: 61

[phoenix]

You do need a DNS server behind the NAT with an MX record (as well as the A record) for correct DNS resolution and it's probably the cause of this problem.