Endian Firewall

Comunidade Brasileira de Endian Firewall

1. 

   issisvan
   Membro

   Bom dia Pessoal,

   Estou instalando o endian 2.4 em um cliente porém a autenticação do proxy não funciona, eu tenho um AD 2008 Server, coloco NTLM quando vou navegar fica so solicitando a senha e não vai adiante porém não apresenta erro nenhum no EFW 2.4, e ao colocar LDAP ele da apresenta a menssagem que nao consegue fazer conexão com o LDAP, já fiz inumeros testes tenho outra aplicações que conectam LDAP neste servidor e funciona perfeitamente, alguem já fez funcionar em um domínio que so tem windows 2008 com AD??? porque quando tenho 2003 aponto para o EFW buscar os usuário nele e funciona perfeito mas com windows 2008 não vai nem com reza brava.....

   Obrigado pessoal!

   Publicado 1 year atrás #
2. 

   lucas.souza
   Membro

   Bom dia ,

   Estou com o mesmo problema , ja postei em outro topico , mas foi encerrado .

   Jun 21 05:22:26 efw-1277115338 winbindd[7357]: initialize_winbindd_cache: clearing cache and re-creating with version number 1
   Jun 21 05:22:26 efw-1277115338 winbindd[7357]: [2010/06/21 05:22:26, 0] winbindd/winbindd_util.c:init_domain_list(740)
   Jun 21 05:22:26 efw-1277115338 winbindd[7357]: Could not fetch our SID - did we join?
   Jun 21 05:22:26 efw-1277115338 winbindd[7357]: [2010/06/21 05:22:26, 0] winbindd/winbindd.c:main(1286)
   Jun 21 05:22:26 efw-1277115338 winbindd[7357]: unable to initialize domain list
   Jun 21 05:22:30 efw-1277115338 winbindd[7469]: [2010/06/21 05:22:30, 0] winbindd/winbindd_cache.c:initialize_winbindd_cache(2379)
   Jun 21 05:22:30 efw-1277115338 winbindd[7469]: initialize_winbindd_cache: clearing cache and re-creating with version number 1
   Jun 21 05:22:30 efw-1277115338 winbindd[7469]: [2010/06/21 05:22:30, 0] winbindd/winbindd_util.c:init_domain_list(740)
   Jun 21 05:22:30 efw-1277115338 winbindd[7469]: Could not fetch our SID - did we join?
   Jun 21 05:22:30 efw-1277115338 winbindd[7469]: [2010/06/21 05:22:30, 0] winbindd/winbindd.c:main(1286)
   Jun 21 05:22:30 efw-1277115338 winbindd[7469]: unable to initialize domain list
   Jun 21 05:22:32 efw-1277115338 winbindd[7563]: [2010/06/21 05:22:32, 0] winbindd/winbindd_cache.c:initialize_winbindd_cache(2379)
   Jun 21 05:22:32 efw-1277115338 winbindd[7563]: initialize_winbindd_cache: clearing cache and re-creating with version number 1
   Jun 21 05:22:32 efw-1277115338 winbindd[7563]: [2010/06/21 05:22:32, 0] winbindd/winbindd_util.c:init_domain_list(740)
   Jun 21 05:22:32 efw-1277115338 winbindd[7563]: Could not fetch our SID - did we join?
   Jun 21 05:22:32 efw-1277115338 winbindd[7563]: [2010/06/21 05:22:32, 0] winbindd/winbindd.c:main(1286)
   Jun 21 05:22:32 efw-1277115338 winbindd[7563]: unable to initialize domain list
   Jun 21 05:22:39 efw-1277115338 winbindd[7599]: [2010/06/21 05:22:39, 0] winbindd/winbindd_cache.c:initialize_winbindd_cache(2379)
   Jun 21 05:22:39 efw-1277115338 winbindd[7599]: initialize_winbindd_cache: clearing cache and re-creating with version number 1
   Jun 21 05:22:39 efw-1277115338 winbindd[7601]: [2010/06/21 05:22:39, 0] libsmb/cliconnect.c:cli_session_setup_spnego(877)
   Jun 21 05:22:39 efw-1277115338 winbindd[7601]: Kinit failed: Clock skew too great
   Jun 21 05:22:40 efw-1277115338 winbindd[7599]: [2010/06/21 05:22:40, 0] libsmb/cliconnect.c:cli_session_setup_spnego(877)
   Jun 21 05:22:40 efw-1277115338 winbindd[7599]: Kinit failed: Clock skew too great
   Jun 21 05:22:40 efw-1277115338 winbindd[7601]: [2010/06/21 05:22:40, 0] rpc_client/cli_pipe.c:cli_pipe_verify_schannel(353)
   Jun 21 05:22:40 efw-1277115338 winbindd[7601]: cli_pipe_verify_schannel: auth_len 56.
   Jun 21 05:23:12 efw-1277115338 winbindd[7621]: [2010/06/21 05:23:12, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 05:23:12 efw-1277115338 winbindd[7621]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 7599 is running.
   Jun 21 05:23:44 efw-1277115338 winbindd[7632]: [2010/06/21 05:23:44, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 05:23:44 efw-1277115338 winbindd[7632]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 7599 is running.
   Jun 21 05:24:16 efw-1277115338 winbindd[7646]: [2010/06/21 05:24:16, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 05:24:16 efw-1277115338 winbindd[7646]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 7599 is running.
   Jun 21 15:25:26 efw-1277115338 winbindd[8135]: [2010/06/21 15:25:26, 0] winbindd/winbindd_cache.c:initialize_winbindd_cache(2379)
   Jun 21 15:25:26 efw-1277115338 winbindd[8135]: initialize_winbindd_cache: clearing cache and re-creating with version number 1
   Jun 21 15:25:26 efw-1277115338 winbindd[8136]: [2010/06/21 15:25:26, 0] rpc_client/cli_pipe.c:cli_pipe_verify_schannel(353)
   Jun 21 15:25:26 efw-1277115338 winbindd[8136]: cli_pipe_verify_schannel: auth_len 56.
   Jun 21 15:25:59 efw-1277115338 winbindd[8155]: [2010/06/21 15:25:59, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:25:59 efw-1277115338 winbindd[8155]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8135 is running.
   Jun 21 15:26:31 efw-1277115338 winbindd[8169]: [2010/06/21 15:26:31, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:26:31 efw-1277115338 winbindd[8169]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8135 is running.
   Jun 21 15:26:50 efw-1277115338 winbindd[8179]: [2010/06/21 15:26:50, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(240)
   Jun 21 15:26:50 efw-1277115338 winbindd[8179]: startsmbfilepwent_internal: file /etc/samba/smbpasswd did not exist. File successfully created.
   Jun 21 15:27:03 efw-1277115338 winbindd[8200]: [2010/06/21 15:27:03, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:27:03 efw-1277115338 winbindd[8200]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8135 is running.
   Jun 21 15:27:35 efw-1277115338 winbindd[8211]: [2010/06/21 15:27:35, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:27:35 efw-1277115338 winbindd[8211]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8135 is running.
   Jun 21 15:28:07 efw-1277115338 winbindd[8225]: [2010/06/21 15:28:07, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:28:07 efw-1277115338 winbindd[8225]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8135 is running.
   Jun 21 15:28:41 efw-1277115338 winbindd[8292]: [2010/06/21 15:28:41, 0] winbindd/winbindd_cache.c:initialize_winbindd_cache(2379)
   Jun 21 15:28:41 efw-1277115338 winbindd[8292]: initialize_winbindd_cache: clearing cache and re-creating with version number 1
   Jun 21 15:28:42 efw-1277115338 winbindd[8293]: [2010/06/21 15:28:42, 0] rpc_client/cli_pipe.c:cli_pipe_verify_schannel(353)
   Jun 21 15:28:42 efw-1277115338 winbindd[8293]: cli_pipe_verify_schannel: auth_len 56.
   Jun 21 15:28:46 efw-1277115338 winbindd[8403]: [2010/06/21 15:28:46, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:28:46 efw-1277115338 winbindd[8403]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8292 is running.
   Jun 21 15:28:48 efw-1277115338 winbindd[8497]: [2010/06/21 15:28:48, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:28:48 efw-1277115338 winbindd[8497]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8292 is running.
   Jun 21 15:28:50 efw-1277115338 winbindd[8293]: [2010/06/21 15:28:50, 0] rpc_client/cli_pipe.c:cli_pipe_verify_schannel(353)
   Jun 21 15:28:50 efw-1277115338 winbindd[8293]: cli_pipe_verify_schannel: auth_len 56.
   Jun 21 15:29:20 efw-1277115338 winbindd[8545]: [2010/06/21 15:29:20, 0] lib/pidfile.c:pidfile_create(120)
   Jun 21 15:29:20 efw-1277115338 winbindd[8545]: ERROR: winbindd-winbind.conf is already running. File /var/run/winbindd-winbind.conf.pid exists and process id 8292 is running.
   Jun 21 15:29:45 efw-1277115338 winbindd[8293]: [2010/06/21 15:29:45, 0] rpc_client/cli_pipe.c:cli_pipe_verify_schannel(353)
   Jun 21 15:29:45 efw-1277115338 winbindd[8293]: cli_pipe_verify_schannel: auth_len 56.

   Publicado 1 year atrás #
3. 

   Albaney Baylão
   Membro

   Já leu? http://kb.endian.com/entry/49/

   Publicado 1 year atrás #
4. 

   lucas.souza
   Membro

   Albaney Baylão , Ja fiz esse procedimento , mas sem sucesso .

   Eu consigo ler os grupos e usuários do AD na aba Access Policy , mas o problema é na autenticação .

   Publicado 1 year atrás #
5. 

   issisvan
   Membro

   Ja tentei fazer um monte de coisa instalei o PFSENSE e autentica na boa porém quero utilizar o endian pela interface mais amigavel, no windows 2003 funciona perfeito NTLM e LDAP porém no 2008 nem LDAP não vai pra frente nas versões anteriores funciona?o Preciso implementar e quando eu seleciono um grupo salvo e aplico apresenta a menssagem: "Could Not read rule '0', bacause: list index out of range." mas o grupo q estou pegando é de dentro da OU especificada no DN find:

   Pessoal preciso de uma solução se alguem pude dar uma luz, fico muito grato!

   Publicado 1 year atrás #
6. 

   maurelio
   Membro

   Pessoal,

   Alguém já consegui fazer o Endian 2.4 funcionar com autenticação NTLM ou LDAP?

   Já tentei as duas e não estou conseguindo colocar no ar.

   []'s
   MA

   Publicado 1 year atrás #
7. 

   issisvan
   Membro

   Pessoal,

   Efetuei um teste com 2.3 e funcionou perfeitamente é algum BUG do 2.4 a autenticação via LDAP usando o AD do W2k8R2 funcionou no 2.3 e ja esta em produção, mas no 2.4 infelizmente não foi,

   Abraço a todos espero em breve efetuar novos teste e ficar tudo ok, porque o erro acontece mesmo atualizando o endian com o (efw-update),

   Valeu

   Publicado 1 year atrás #
8. 

   wendel
   Membro

   Pessoal, alguma novidade sobre o topico ? alguem mais testou pois estou na mesma situação do issisvan.

   Publicado 1 year atrás #
9. 

   Eduardo Jonck
   Membro

   Pessoal, apos ter feito as configurações necessárias, é obrigatório dar os comandos via putty:

   chown -R root:squid /var/cache/samba/winbindd_privileged

   /etc/init.d/winbind restart

   pois esses comandos são cruciais para o AD se comunicar com o Endian, através do SAMBA
   Eu Testei aqui é está tudo certinho, qualquer duvida da configuração completa é so postar que estarei postando a resposta valeu!!!!

   Publicado 6 months atrás #

RSS feed for this topic

Resposta

Você deve fazer login para publicar.