Samba/Winbind issues joing to Active directory domain

active-directorynsswitch.confsambawinbind

I'm currently in the process of setting up winbind/samba and getting a few issues.

I can test connectivity with wbinfo fine:

[root@buildmirror ~]# wbinfo -u
hostname     username
administrator
guest
krbtgt
username


[root@buildmirror ~]# wbinfo -a username%password
plaintext password authentication succeeded
challenge/response password authentication succeeded

however when I do a getent I don't get any AD accounts returned

[root@buildmirror ~]# getent passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/var/spool/mail:/sbin/nologin
uucp:x:10:14:uucp:/var/spool/uucp:/sbin/nologin
operator:x:11:0:operator:/root:/sbin/nologin
puppet:x:52:52:Puppet:/var/lib/puppet:/sbin/nologin

my nsswitch looks like this:

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

#hosts:     db files nisplus nis dns
hosts:      files dns

and I'm definitely joined to the domain:

[root@buildmirror ~]# net ads info
LDAP server: 192.168.4.4
LDAP server name: pdc.domain.local
Realm: domain.local
Bind Path: dc=DOMAIN,dc=LOCAL
LDAP port: 389
Server time: Sun, 05 Aug 2012 17:11:27 BST
KDC server: 192.168.4.4
Server time offset: -1

So what am I missing?

Best Answer

Do you have the following lines in /etc/samba/smb.conf?

winbind enum users = yes
winbind enum groups = yes

Related Solutions

Active Directory – How to Find Name of Active Directory Domain Controller

On any computer, that has DNS configured to use AD's DNS server do:

Start -> Run -> nslookup

set type=all
_ldap._tcp.dc._msdcs.DOMAIN_NAME

Replace DOMAIN_NAME with the actual domain name e.g. example.com. Read more here.

Samba Permissions – I’m going to throw it!

This might help. I do something similar, but only one share is open to the group's users. Other shares are read-only except for a single maintainer user. The [global] section of my smb.conf is almost identical to yours, except I don't use the force create/directory mode directives (in my case, they'd interfere with the other shares).

Here's the share definition:

[shared stuff]
        comment = blah, blah, etc
        path = /path/to/share
        write list = @sambagroup
        force group = +sambagroup
        read only = yes
        directory mask = 0775
        create mask = 0664
        guest ok = yes
        invalid users = root
        case sensitive = True
        default case = lower
        preserve case = yes
        short preserve case = yes

The important stuff here are these:

read only = yes -- by default, read only.
guest ok = yes -- guests can browse.
write list = @sambagroup -- Authenticated members of sambagroup can write.
force group = +sambagroup -- The + means that the force only applies to existing members of sambagroup. They're already the only ones who can write. I think, without the +, guest is given sambagroup credentials, which is not wanted (particularly with the write list directive above).
directory mask = 0775
create mask = 0664

These do exactly what you want yours to do: "drwxrwxr-x" on directories, "rwxrwxr-x" on files, and newly created files are owned by the user and sambagroup. The maintainers of the other shares get the same permissions as everyone else when working in shared stuff, and permissions & groups are normal when they work in the other shares.

My smb.conf has been working with only minor tweaks through several different versions of Samba, and currently is used with Samba 3.2.5. I never had it running on Ubuntu 8.04, but it ran on Ubuntu 7.04 for a long time before getting migrated to a recent Debian Lenny install.

Related Topic