the barracuda is internal to our network. it is behind a firewall. my exchange server is not a domain controller just a mail server.
below is the message that i get from the test LDAP in the barracuda
could not set open file limit to 8192: Operation not permitted
lookup order: fb
listening on localhost/56656
answering client connection request from 127.0.0.1/56657
received from 127.0.0.1/56657: GET administrator@op%2dtn.org
email address: administrator@op-tn.org
administrator@op-tn.org not found in cache
LDAP test succeeded
requesting LDAP connection to 192.168.10.4/389 for 127.0.0.1/56657
binding with '(null)' / '(null)'
failed to bind to LDAP directory 192.168.10.4/389: Can't contact LDAP server
resetting LDAP connection to 192.168.10.4/389
reaping LDAP connection to 192.168.10.4/389
delisting LDAP connection to 192.168.10.4/389
LDAP connect failed on user administrator@op-tn.org: Connection failed
telling 127.0.0.1/56657: FAILED
received from 127.0.0.1/56657: QUIT
hanging up on client 127.0.0.1/56657
exiting on SIGTERM
if i point the Barracuda towards my DC for the LDAP settings will that hurt anything with the mail??
Main Topics
Browse All Topics





by: ziggykPosted on 2008-05-01 at 12:57:47ID: 21482097
Did you set up an account in Active Directory for the barracuda to use?
Is your barracuda internal to your domain or external?
Is your Exchange server also a domain controller? If not, you need to tell the barracuda to use the DC not the Exchange server.
Could you post the message that the barracuda returns when you click the Test LDAP button? It should pop up with a "LDAP Test Unsuccessful (details below)" box.
FYI, when you telnet into port 389 it should return nothing. So, your barracuda could be talking to the LDAP.