I want to authenticate via Active Directory on a CentOS 6.4 server.

wbinfo -u and wbinfo -g display the domain users/groups. Authentication via wbinfo -a DOMAIN+user works. Authentication via kinit user works.

But for some reason, getent passwd and getent group only display local users/groups. I have found a lot of forum posts about this topic, but none provided a working solution.

Here is my /etc/samba/smb.conf:

        workgroup = DOMAIN
        realm = DOMAIN.LOCAL
        security = ADS
        max log size = 50
        template shell = /bin/bash
        winbind separator = +
        winbind enum users = Yes
        winbind enum groups = Yes
        winbind use default domain = Yes
        idmap config DOMAIN : schema_mode = rfc2307
        idmap config DOMAIN : range = 10000000-29999999
        idmap config DOMAIN : default = yes
        idmap config DOMAIN : backend = ad
        idmap config * : range = 20000-29999
        idmap config * : backend = tdb


 default_realm = DOMAIN.LOCAL
 dns_lookup_realm = false
 dns_lookup_kdc = false
 ticket_lifetime = 24h
 renew_lifetime = 7d
 forwardable = true

  admin_server = ADSERVER.DOMAIN.LOCAL


passwd:     files winbind
shadow:     files winbind
group:      files winbind

The AD server runs Windows Small Business Server 2008.

4 Answers 4


I had the same problem. In my case it turned out I forgot to install the libnss-winbind and libpam-winbind packages on Ubuntu.

Hope this helps someone looking here with this problem ;)

  • Hello, welcome to superuser. your answer is not an answer and should be a comment or reworded into a question with your particular problems. Please see help at the top of the page to find guidance on how to use superuser Thankyou
    – mic84
    Sep 20, 2016 at 8:35
  • @mic84 Well, I could reword into a question, but the question would be same as this question, because I had exactly the same symptoms. Wouldn't it be better to have all possible solutions to these symptons in this place? Or would you rather create a new identical question for each one?
    – acidtv
    Sep 21, 2016 at 7:22
  • 5
    Your answer, be it a real answer or not, in fact helped me. Since the two libs aren't installed by default this is easily overlooked and I was glad someone took the time to post this at a place you eventually run into when looking for answers to that problem. Apr 26, 2017 at 9:10
  • 1
    This was the solution for me on Ubuntu 16.04 LTS. Aug 18, 2020 at 3:25

I used backend = ad, which requires additional configuration on the AD server. What I really wanted is backend = rid, everything works fine now.


None of the above worked for me on CentOS 7. What solved the problem was to open


and suffix the following lines:

passwd:     files sss
shadow:     files sss
group:      files sss

with "winbind" as follows:

passwd:     files sss winbind
shadow:     files sss winbind
group:      files sss winbind

On saving the changes to the file, all of the following commands:

id <AD user name>
getent passwd
getent group

began working. No restart of smbd / nmbd / winbindd was required.


That's how I solved the problem.

change /etc/samba/smb.conf

change idmap config *:backend = ab to idmap config *:backend = tdb

This's OK。

this is my smb.conf

  • well, I have another problem after solving this problem.I have two centos machines, all joined in the Active Directory, and when I looked at the user id with getent passwd, I found that the same user was mapped to two different id on different machines. Aug 3, 2017 at 10:41
  • finally, I solved this problem.i change idmap config *:backend = tdb to idmap config *:backend = rid , and the user id of all machine is same. there is a link to explain it,but you have to unstand chinese. 使用rid作为存储用户id的方式 Aug 3, 2017 at 10:55
  • It appears you might have your own question. It is not possible for us to answer your question, since you submitted your question as an answer, and your non-english link (which contains the answer to your question) isn't helpful to the community as a large. Keep in mind the author's question while similar was not identical to your question (hence the reason they accepted an entirely different solution to their problem) and thus it's difficult to see the usefulness in your non-english solution.
    – Ramhound
    Aug 21, 2017 at 19:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.