Jorge.
Sou de novo... rsrsrs
Bom... tentei novamente e nada... o estranho q com a versão 2.0 do zentyal eu tive problemas sim, mas eram com a sincronização de senhas, já com a versão 2.2 não passa da ativação do serviço "Usuários e Grupos".
Como vc disse que tem ele rodando ai sem problema, você poderia nos dar uma "luz" sobre isso?? Segui a documentação do zentyal ao "pé da letra" e nada...
A única coisa estranha que notei foi que quando pingo o AD pelo nome a partir do Zentyal ele resolve o nome OK, mas o contrário não acontece. Fora isso, parece estar tudo ok.
Outro detalhe que acredito não ser o problema, mas vai que... estou rodando o AD e o Zentyal a partir de máquinas virtuais usando o Virtual Box da Oracle.
Segue abaixo o conteúdo do zentyal.log :
2011/10/10 09:38:16 INFO> GlobalImpl.pm:539 EBox::GlobalImpl::saveAllModules - Saving config and restarting services: firewall users
2011/10/10 09:38:16 INFO> Base.pm:228 EBox::Module::Base::save - Restarting service for module: firewall
2011/10/10 09:38:18 INFO> GlobalImpl.pm:653 EBox::GlobalImpl::saveAllModules - Changes saved successfully
2011/10/10 09:38:31 INFO> ServiceManager.pm:631 EBox::ServiceManager::_getMD5 - File /etc/cron.d/zentyal-users does not exist. So we won't compute its digest
2011/10/10 09:38:31 INFO> ServiceManager.pm:631 EBox::ServiceManager::_getMD5 - File /etc/ldap.secret does not exist. So we won't compute its digest
2011/10/10 09:38:31 INFO> ServiceManager.pm:631 EBox::ServiceManager::_getMD5 - File /etc/cron.d/zentyal-users does not exist. So we won't compute its digest
2011/10/10 09:38:32 INFO> ServiceManager.pm:631 EBox::ServiceManager::_getMD5 - File /etc/ldap.secret does not exist. So we won't compute its digest
2011/10/10 09:38:33 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command set -e
ldapadd -H 'ldapi://' -Y EXTERNAL -c -f /var/lib/zentyal/tmp//slapd-master.ldif
ldapadd -H 'ldapi://' -Y EXTERNAL -c -f /var/lib/zentyal/tmp//slapd-master-db.ldif failed.
Error output: ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1)
Command output: .
Exit value: 255
2011/10/10 09:38:33 WARN> Setup.pm:134 EBox::UsersAndGroups::Setup::__ANON__ - Trying to setup master ldap failed, exit value: 255
2011/10/10 09:38:33 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2011/10/10 09:38:35 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2011/10/10 09:38:37 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2011/10/10 09:38:38 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2011/10/10 09:38:39 ERROR> Ldap.pm:1107 EBox::Ldap::safeConnect - FATAL: Couldn't connect to LDAP server: ldapi://%2fvar%2frun%2fslapd%2fldapi
2011/10/10 09:38:39 ERROR> ConfigureModuleController.pm:74 EBox::CGI::ServiceModule::ConfigureModuleController::__ANON__ - Failed to enable: FATAL: Couldn't connect to LDAP server: ldapi://%2fvar%2frun%2fslapd%2fldapi
2011/10/10 09:44:40 ERROR> Base.pm:358 EBox::CGI::Base::__ANON__ - Software caused connection abort at /usr/share/perl5/HTML/Mason/Request.pm line 127.
Olha um teste que fiz a partir do shell do zentyal:
root@zentyal:/var/log/zentyal# ldapsearch -x -h 192.168.3.100 -p 389 -s base -b "" "objectClass=*" namingContexts
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: objectClass=*
# requesting: namingContexts
#
#
dn:
namingContexts: DC=xxxxx2,DC=com
namingContexts: CN=Configuration,DC=xxxxx2,DC=com
namingContexts: CN=Schema,CN=Configuration,DC=xxxxx2,DC=com
namingContexts: DC=DomainDnsZones,DC=xxxxx2,DC=com
namingContexts: DC=ForestDnsZones,DC=xxxxx2,DC=com
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
Se puder nos ajudar nessa questão...
Obrigado novamente !
Att.,
Lucas Justino.