Synchronization LDAP

[s-mbs@…]

In a network there is a domain with the principal directory. The proxy server, without errors is connected. Synchronization of the main thing and a server proxy happen normally. The error has arisen in an email server installation time, as selected machine. I have specified the master the directory and the password. At unit activation "Users and Groups" the message has been produced: "Failed to enable: FATAL: Couldn't connect to LDAP server: ldap://192.168.0.211".

[s-mbs@…]

Trace Failed to enable: FATAL: Couldn't connect to LDAP server: ldap://192.168.0.211 at /usr/share/perl5/EBox/CGI/ServiceModule/ConfigureModuleController.pm line 74 EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController?=HASH(0x7f...') called at /usr/share/perl5/EBox/CGI/Base.pm line 262 EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController?=HASH(0x7f...') called at /usr/share/perl5/EBox/CGI/Run.pm line 120 EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController?', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 35 ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec?=SCALAR(0x7f8e75658d40)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204 eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204 ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7f8e7565bf80)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7f8e7565bf80)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31 ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec?=SCALAR(0x7f8e75658d40)') called at -e line 0 eval {...} called at -e line 0

[christophe@…]

Did you install your mail server on another server ? or in the ldap server ? Because you need open ldap port (389) in the master if you want connect your ldap to slave machine

[jacalvo@…]

When enabling the slave, the master should be up and running and needs to be reachable, maybe this is a firewall problem. Please reopen only if you are sure the master and the slave are mutually reachable. Thanks.