Hi !
Thank you for your suggestions.
There is no Samba running on this machine.
The Windows AD running in a VM has it's own IP on it's own physical
network card in bridged mode.
Since the mail server (on a different machine on the same network) can
access the Windows AD and use LDAP, it doesn't seem as this is a port
problem.
I can reach (connect) to the LDAP (Windows) server with telnet from the
SOGo machine.
I can run ldapsearch and get correct results from the SOGo machine.
I can ping the LDAP (Windows) serve from the SOGo machine.
So it seems to be a local SOGo problem I'm afraid.
Regards,
Sigurd Holter
Den 27.10.2014 23:01, skrev Steve Ankeny:
Do you have a collision between ports on the server?
LDAP will use port 389, but Samba wants that port also.
When I installed Samba, I had to change my LDAP port so it wouldn't
collide with Samba
Do you have a process that's grabbing the port before LDAP can use it?
On 10/27/2014 10:25 AM, Stefan Klatt wrote:
Hi Sigurd,
can you reach your LDAP server with telnet (on the used port) if your
SOGo server hangs?
Stefan
--
[email protected]
https://inverse.ca/sogo/lists
