Systems Management Question

Error to create LDAP Label

03/02/2018 1069 views
Hi guys!

I'm trying to create a LDAP label, with my advanced search, but i got error.

(&(sAMAccountName=KBOX_USER_NAME)(memberOf=CN=MA - ** Acess,OU=.MA Distribution Lists,OU=MA,DC=k***n,DC=net))

Testando configurações de rótulo do protocolo LDAP...
Testar a conexão "MA - ** Acess" com: *** na porta: ***
OK: conexão bem-sucedida.
OK: configuração da versão 3 do protocolo com êxito.
OK: configuração da opção 0 de REFERÊNCIAS DE LDAP realizada com êxito.
OK: pesquisa de autenticação usando as credenciais fornecidas pelo protocolo LDAP bem-sucedida.
Aplicando filtro de pesquisa: [(&(sAMAccountName=*_NAME)(memberOf=CN=MA *** Acesso,OU=.MA Distribution Lists,OU=MA,DC=k****n,DC=net))]
OK: pesquisa do protocolo LDAP (com filtro [(&(sAMAccountName=*_NAME)(memberOf=CN=MA - *** Acess,OU=.MA Distribution Lists,OU=MA,DC=k***n,DC=net))]) bem-sucedida.
Erro: falha em pesquisa do protocolo LDAP. Nenhuma entrada encontrada.
Erro: teste de LDAP com falha. Encerrando conexão.

Where am i going wrong?
2 Comments   [ + ] Show comments


  • I believe is fine...

    Could you translate to English the last two lines?

    Also what type of LDAP label? (user, device)

    What are you trying to capture or filter?
  • Channeler, srry, i forgot to translate.

    Error: LDAP protocol lookup failed. No entries were found.
    Error: Failed LDAP test. Terminating connection.

    Its a User LDAP, i trying to catch users from the LD
    Its a filter

All Answers

As far as I know, you cannot use wildcards (e.g. "*" ) in LDAP queries from KACE
Answered 05/16/2018 by: JasonEgg
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ