Samba & Winbind & Kerberos & AD 2008

Support Debian
#1

Bonjour,

Je poste ici pour avoir une soluce sur mon souci qui m’aura gavé pendnt 5 jours, faut dire que c’est pas toujours simple !

Actuellement sur Linux ***** 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux qui est une Debian Squeeze, je tente d’installer un serveur de partage fichiers d’entreprise avec authentication sur [Active Directory] ET [Compte Local Samba] en fallback.

De ce fait je vous décris toutes les manips effectuées:

root@*****:/etc/# nano /etc/apt/sources.list
=> ajout ligne des backports de squeeze: deb backports.debian.org/debian-backports squeeze-backports main

root@*****:/etc/# nano /etc/network/interfaces
=> ajout résolution noms DNS correct

root@*****:/etc/# aptitude install ntp ntpdate krb5-users libpam-krb5 krb5-config

Modifs effectuées sur Kerberos & NTP & SNMP
kinit et klist: OK.
NTP: date OK.
SNMP: retour traps OK.

Winbind v3.6.6
Samba v3.6.6

Modif fichiers de config smb.conf:

[code]#======================= Global Settings =======================

[global]

log level = 10

Browsing/Identification

Change this to the workgroup/NT-domain name your Samba server will part of

workgroup = tata

added by ffrancois in installation in case of Kerberos

realm = TATA.FR

server string is the equivalent of the NT Description field

server string = %h server

Windows Internet Name Serving Support Section:

WINS Support - Tells the NMBD component of Samba to enable its WINS Server

wins support = no

WINS Server - Tells the NMBD components of Samba to be a WINS Client

Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

wins server =

This will prevent nmbd to search for NetBIOS names through DNS.

dns proxy = no

What naming service and in what order should we use to resolve host names

to IP addresses

; name resolve order = lmhosts host wins bcast

Networking

The specific set of interfaces / networks to bind to

This can be either the interface name or an IP address/netmask;

interface names are normally preferred

; interfaces = 127.0.0.0/8 eth0

Only bind to the named interfaces and/or networks; you must use the

‘interfaces’ option above to use this.

It is recommended that you enable this feature if your Samba machine is

not protected by a firewall or is a firewall itself. However, this

option cannot handle dynamic or non-broadcast interfaces correctly.

; bind interfaces only = yes

Debugging/Accounting

This tells Samba to use a separate log file for each machine

that connects

log file = /var/log/samba/log.%m

Cap the size of the individual log files (in KiB).

max log size = 1000

If you want Samba to only log through syslog then set the following

parameter to ‘yes’.

syslog only = no

We want Samba to log a minimum amount of information to syslog. Everything

should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log

through syslog you should set the following parameter to something higher.

syslog = 0

Do something sensible when Samba crashes: mail the admin a backtrace

panic action = /usr/share/samba/panic-action %d

####### Authentication #######

“security = user” is always a good idea. This will require a Unix account

in this server for every user accessing the server. See

/usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html

in the samba-doc package for details.

security = ads

You may wish to use password encryption. See the section on

‘encrypt passwords’ in the smb.conf(5) manpage before enabling.

encrypt passwords = true

If you are using encrypted passwords, Samba will need to know what

password database type you are using.

passdb backend = tdbsam

obey pam restrictions = yes

This boolean parameter controls whether Samba attempts to sync the Unix

password with the SMB password when the encrypted SMB password in the

passdb is changed.

unix password sync = yes

For Unix password sync to work on a Debian GNU/Linux system, the following

parameters must be set (thanks to Ian Kahan <kahan@informatik.tu-muenchen.de for

sending the correct chat script for the passwd program in Debian Sarge).

passwd program = /usr/bin/passwd %u
passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .

This boolean controls whether PAM will be used for password changes

when requested by an SMB client instead of the program listed in

‘passwd program’. The default is ‘no’.

pam password change = yes

This option controls how unsuccessful authentication attempts are mapped

to anonymous connections

map to guest = bad user

########## Domains ###########

Is this machine able to authenticate users. Both PDC and BDC

must have this setting enabled. If you are the BDC you must

change the ‘domain master’ setting to no

; domain logons = yes

The following setting only takes effect if ‘domain logons’ is set

It specifies the location of the user’s profile directory

from the client point of view)

The following required a [profiles] share to be setup on the

samba server (see below)

; logon path = \%N\profiles%U

Another common choice is storing the profile in the user’s home directory

(this is Samba’s default)

logon path = \%N%U\profile

The following setting only takes effect if ‘domain logons’ is set

It specifies the location of a user’s home directory (from the client

point of view)

; logon drive = H:

logon home = \%N%U

The following setting only takes effect if ‘domain logons’ is set

It specifies the script to run during logon. The script must be stored

in the [netlogon] share

NOTE: Must be store in ‘DOS’ file format convention

; logon script = logon.cmd

This allows Unix users to be created on the domain controller via the SAMR

RPC pipe. The example command creates a user account with a disabled Unix

password; please adapt to your needs

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos “” %u

This allows machine accounts to be created on the domain controller via the

SAMR RPC pipe.

The following assumes a “machines” group exists on the system

; add machine script = /usr/sbin/useradd -g machines -c “%u machine account” -d /var/lib/samba -s /bin/false %u

This allows Unix groups to be created on the domain controller via the SAMR

RPC pipe.

; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

If you want to automatically load your printer list rather

than setting them up individually then you’ll need this

load printers = yes

lpr(ng) printing. You may wish to override the location of the

printcap file

; printing = bsd
; printcap name = /etc/printcap

CUPS printing. See also the cupsaddsmb(8) manpage in the

cupsys-client package.

; printing = cups
; printcap name = cups

############ Misc ############

Using the following line enables you to customise your configuration

on a per machine basis. The %m gets replaced with the netbios name

of the machine that is connecting

; include = /home/samba/etc/smb.conf.%m
include = /etc/samba/.conf
include = /etc/samba/.conf

Most people will find that this option gives better performance.

See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html

for details

You may want to add the following on a Linux system:

SO_RCVBUF=8192 SO_SNDBUF=8192

socket options = TCP_NODELAY

The following parameter is useful only if you have the linpopup package

installed. The samba maintainer and the linpopup maintainer are

working to ease installation and configuration of linpopup and samba.

; message command = /bin/sh -c ‘/usr/bin/linpopup “%f” “%m” %s; rm %s’ &

Domain Master specifies Samba to be the Domain Master Browser. If this

machine will be configured as a BDC (a secondary logon server), you

must set this to ‘no’; otherwise, the default behavior is recommended.

domain master = auto

Some defaults for winbind (make sure you’re not using the ranges

for something else.)

idmap backend = tdb
idmap uid = 10000 - 20000
idmap gid = 10000 - 20000
idmap config TATA : backend = ad
idmap config TATA : schema_mode = rfc2307
idmap config TATA : range = 20001 - 40000
template shell = /bin/bash

The following was the default behaviour in sarge,

but samba upstream reverted the default because it might induce

performance issues in large organizations.

See Debian bug #368251 for some of the consequences of not

having this setting and smb.conf(5) for details.

winbind enum groups = yes
winbind enum users = yes
winbind use default domain = Yes

Setup usershare options to enable non-root users to share folders

with the net usershare command.

Maximum number of usershare. 0 (default) means that usershare is disabled.

; usershare max shares = 100

Allow users who’ve been granted usershare privileges to create

public shares, not just authenticated ones

; usershare allow guests = yes[/code]

Modif fichier de conf nsswitch.conf:

[code]# /etc/nsswitch.conf

Example configuration of GNU Name Service Switch functionality.

If you have the glibc-doc-reference' andinfo’ packages installed, try:

`info libc “Name Service Switch”’ for information about this file.

passwd: compat winbind
group: compat winbind
shadow: compat

hosts: files dns
networks: files

protocols: db files
services: db files
ethers: db files
rpc: db files

netgroup: nis[/code]

Serveur debian ajouté sur le Domaine TATA.FR, pas de souci particulier, le net ads testjoin est Ok.
net cache flush
reboot
kinit administrateur
klist
net ads info
wbinfo -u => liste les utilisateurs du domaine: OK.
wbinfo -g => liste les groupes du domaine: OK.
wbinfo -m => liste bien TATA.FR
wbinfo -n administrateur => S-1-5-21-1135005479-1549511432-1800673368-500 SID_USER (1)
wbinfo -s S-1-5-21-1135005479-1549511432-1800673368-500 => TATA\administrateur (1)
wbinfo -S S-1-5-21-1135005479-1549511432-1800673368-500 => failed to call wbcSidToUid: WBC_ERR_DOMAIN_NOT_FOUND - Could not convert sid S-1-5-21-1135005479-1549511432-1800673368-500 to uid

En security = ADS (je souhaite garder les utilisateurs locaux et ceux de AD, en security = user ça fonctionne)
smbclient “\\192.168.11.79\coin” -U coin
Enter coin’s password:
Domain=[TATA] OS=[Unix] Server=[Samba 3.6.6]
tree connect failed: NT_STATUS_ACCESS_DENIED

Je dois dire que je suis gavé là dessus, winbind est censé mapper tout seul, il n’y a pas lieu d’installer le management dans AD pour les UNIX credentials winbind est censé mapper.

Help !

#2

Bonjour,

Il est très difficile de lire ce post, les balises code devrait corriger cela :wink:
Que donne la commande suivante ?

smbclient "\\\\192.168.11.79\\coin" -U "TATA\coin"
#3

Bonjour,

J’en suis désolé pour le manque de clarté dans le formatage du texte.

Pour le partage en valid user = TATA\coucou

[code]root@*****:~# smbclient “\\192.168.11.79\coucou” -U “coucou” Enter coucou’s password:
Domain=[TATA] OS=[Unix] Server=[Samba 3.6.6]
tree connect failed: NT_STATUS_ACCESS_DENIED

root@*****:~# smbclient “\\192.168.11.79\coucou” -U "TATA\coucou"
Enter TATA\coucou’s password:
Domain=[TATA] OS=[Unix] Server=[Samba 3.6.6]

[/code]

Ça semble fonctionner avec TATA\coucou.

Ce qui est pas normal c’est que winbind ne semble pas vouloir mapper les SID de AD en UID …
Mais même les utilisateurs locaux (avec smbpasswd) ça fonctionne pas avec le paramètre security = ADS, ça ne fonctionne qu’en user.

Je me demande même si ça s’authentifie réellement ou pas sur AD …

Par contre j’ai eu ça une fois:

root@*****:~# net cache flush Couldn't delete entry! key = IDMAP/SID2GID/S-1-5-11 Couldn't delete entry! key = IDMAP/SID2GID/S-1-5-2

#4

Re !

L’arborescence du dossier permet-elle à l’utilisateur de se connecter (droits accès) ?
Par ailleurs qu’en est-il de WinBind ? (j’ai pas trop pris le temps mais une recherche sur google de WBC_ERR_DOMAIN_NOT_FOUND m’a renvoyé vers ca : )
http://samba.2283325.n4.nabble.com/Samba-4-WBC-ERR-DOMAIN-NOT-FOUND-error-td3009676.html

#5

Oui.
J’ai édit le message précédent, TATA\coucou fonctionne avec le droit d’accès, mais j’ai l’impression que ça s’authentifie pas sur AD vu qu’il arrive à se connecter alors que les droits du dossier partagé sont basées sur le compte local linux.

Dossier \coucou => propriétaire coucou:coucou (chmod 777)
Utilisateur coucou en local unix
Utilisateur coucou sur AD
Valid Users = TATA\coucou est ok
Valid Users = coucou est en error

Il semblerait que l’option “auth methods = sam winbind” soit en deprecated sur cette version …

[quote=“Zenitude”]Par ailleurs qu’en est-il de WinBind ? (j’ai pas trop pris le temps mais une recherche sur google de WBC_ERR_DOMAIN_NOT_FOUND m’a renvoyé vers ca : )
http://samba.2283325.n4.nabble.com/Samba-4-WBC-ERR-DOMAIN-NOT-FOUND-error-td3009676.html[/quote]

Les commandes qui sont données fonctionnent toutes sur le lien que tu m’a donné.

wbinfo --own-domain
wbinfo --all-domains
wbinfo --trusted-domains
net cache flush
reboot
kinit administrateur
klist
net ads info
wbinfo -u => liste les utilisateurs du domaine: OK.
wbinfo -g => liste les groupes du domaine: OK.
wbinfo -m => liste bien TATA.FR
wbinfo -n administrateur => S-1-5-21-1135005479-1549511432-1800673368-500 SID_USER (1)
wbinfo -s S-1-5-21-1135005479-1549511432-1800673368-500 => TATA\administrateur (1)

Seule celle-ci échoue:
wbinfo -S S-1-5-21-1135005479-1549511432-1800673368-500 => failed to call wbcSidToUid: WBC_ERR_DOMAIN_NOT_FOUND - Could not convert sid S-1-5-21-1135005479-1549511432-1800673368-500 to uid

Edit:
getent passwd ne fonctionne pas, il ne relève que les utilisateurs locaux !
getent group “groupe” ne fonctionne pas non plus.

Edit 2:
L’ajout de la ligne auth methods = winbind, sam_ignoredomain ne fait fonctionner que la première méthode authentification écrite en paramètre … en l’occurrence winbind, si j’essaie d’accéder avec une authentification locale (smbpasswd), nada, il refuse.

Y a t-il une autre méthode ?

#6

Désolé mais pour ce soir je bloque…

Je regarderais ca de plus prêt demain :text-imsorry:

#7

Bonjour,

Aurais-tu une idée sur ce problème que je rencontre ?
La double authentification devrait normalement être possible, mais le paramètre auth methods= ne semble prendre en compte qu’une seule méthode.

Or, d’après le wiki de Samba, il semblerait que par défaut l’authentification regarde en 1er automatiquement le tdb de samba puis les domaines AD (si présents).

Il me faut absolument cette possibilité.

#8

Bonjour,

Cela m’a l’air résolu,
J’attends une confirmation sur l’état du partage auprès des utilisateurs.

Il semblerait que ce soit un gros manque de documentation qui en est la cause.
J’éditerai ce message dès confirmation pour vous faire partager la configuration.

Edit:

Beaucoup de modifications ont été faites au niveau de Samba / Winbind et j’ai pu (enfin, à peu près) faire fonctionner comme je veux.

:108 Utilisateur: MACHIN\coucou
Pose problème au niveau du default domain, celui ci n’utilise pas le domaine de l’environnement windows que nous utilisons avec Active Directory, mais son propre trusted domain, en gros il s’authentifie localement avec “smbpasswd -a”.

[2012/12/20 12:47:31.534973, 5] auth/auth_util.c:110(make_user_info_map)
Mapping user [MACHIN][coucou] from workstation [PC-92]
[2012/12/20 12:47:31.535880, 5] auth/auth_util.c:131(make_user_info_map)
Mapped domain from [MACHIN] to [hostname] for user [coucou] from workstation [PC-92]

:108 Utilisateur: TATA\coucou
Passe impec.

:108 Utilisateur: TATA\commun
Qui est un utilisateur n’existant pas sur AD mais qui existe en local via “smbpasswd -a”, celui ci ne vérifie même pas localement même avec auth methods = sam, winbind.

[2012/12/20 13:01:14.217565, 5] auth/auth.c:271(check_ntlm_password)
check_ntlm_password: winbind authentication for user [commun] FAILED with error NT_STATUS_NO_SUCH_USER
[2012/12/20 13:01:14.217593, 2] auth/auth.c:319(check_ntlm_password)
check_ntlm_password: Authentication for user [commun] -> [commun] FAILED with error NT_STATUS_NO_SUCH_USER
[2012/12/20 13:01:14.217619, 3] smbd/sesssetup.c:63(do_map_to_guest)
No such user commun [TATA] - using guest account

:108 Utilisateur: hostname\commun
Passe impec.


Configuration File:

[code]#

Sample configuration file for the Samba suite for Debian GNU/Linux.

This is the main Samba configuration file. You should read the

smb.conf(5) manual page in order to understand the options listed

here. Samba has a huge number of configurable options most of which

are not shown in this example

Some options that are often worth tuning have been included as

commented-out examples in this file.

- When such options are commented with “;”, the proposed setting

differs from the default Samba behaviour

- When commented with “#”, the proposed setting is the default

behaviour of Samba but the option is considered important

enough to be mentioned here

NOTE: Whenever you modify this file you should run the command

“testparm” to check that you have not made any basic syntactic

errors.

A well-established practice is to name the original file

“smb.conf.master” and create the “real” config file with

testparm -s smb.conf.master >smb.conf

This minimizes the size of the really used smb.conf file

which, according to the Samba Team, impacts performance

However, use this with caution if your smb.conf file contains nested

“include” statements. See Debian bug #483187 for a case

where using a master file is not a good idea.

#======================= Global Settings =======================

[global]

log level = 10

Browsing/Identification

Change this to the workgroup/NT-domain name your Samba server will part of

workgroup = TATA

added by ffrancois in installation in case of Kerberos

realm = TATA.FR

server string is the equivalent of the NT Description field

server string = %h server

Windows Internet Name Serving Support Section:

WINS Support - Tells the NMBD component of Samba to enable its WINS Server

wins support = no

WINS Server - Tells the NMBD components of Samba to be a WINS Client

Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

wins server =

This will prevent nmbd to search for NetBIOS names through DNS.

dns proxy = no

What naming service and in what order should we use to resolve host names

to IP addresses

; name resolve order = lmhosts host wins bcast

Networking

The specific set of interfaces / networks to bind to

This can be either the interface name or an IP address/netmask;

interface names are normally preferred

; interfaces = 127.0.0.0/8 eth0

Only bind to the named interfaces and/or networks; you must use the

‘interfaces’ option above to use this.

It is recommended that you enable this feature if your Samba machine is

not protected by a firewall or is a firewall itself. However, this

option cannot handle dynamic or non-broadcast interfaces correctly.

; bind interfaces only = yes

Debugging/Accounting

This tells Samba to use a separate log file for each machine

that connects

log file = /var/log/samba/log.%m

Cap the size of the individual log files (in KiB).

max log size = 1000

If you want Samba to only log through syslog then set the following

parameter to ‘yes’.

syslog only = no

We want Samba to log a minimum amount of information to syslog. Everything

should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log

through syslog you should set the following parameter to something higher.

syslog = 0

Do something sensible when Samba crashes: mail the admin a backtrace

panic action = /usr/share/samba/panic-action %d

####### Authentication #######

“security = user” is always a good idea. This will require a Unix account

in this server for every user accessing the server. See

/usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html

in the samba-doc package for details.

security = ads

You may wish to use password encryption. See the section on

‘encrypt passwords’ in the smb.conf(5) manpage before enabling.

encrypt passwords = true

If you are using encrypted passwords, Samba will need to know what

password database type you are using.

passdb backend = tdbsam
obey pam restrictions = yes

This boolean parameter controls whether Samba attempts to sync the Unix

password with the SMB password when the encrypted SMB password in the

passdb is changed.

unix password sync = yes

For Unix password sync to work on a Debian GNU/Linux system, the following

parameters must be set (thanks to Ian Kahan <kahan@informatik.tu-muenchen.de for

sending the correct chat script for the passwd program in Debian Sarge).

passwd program = /usr/bin/passwd %u
passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .

This boolean controls whether PAM will be used for password changes

when requested by an SMB client instead of the program listed in

‘passwd program’. The default is ‘no’.

pam password change = yes

This option controls how unsuccessful authentication attempts are mapped

to anonymous connections

map to guest = bad user

########## Domains ###########

Is this machine able to authenticate users. Both PDC and BDC

must have this setting enabled. If you are the BDC you must

change the ‘domain master’ setting to no

; domain logons = yes

The following setting only takes effect if ‘domain logons’ is set

It specifies the location of the user’s profile directory

from the client point of view)

The following required a [profiles] share to be setup on the

samba server (see below)

; logon path = \%N\profiles%U

Another common choice is storing the profile in the user’s home directory

(this is Samba’s default)

logon path = \%N%U\profile

The following setting only takes effect if ‘domain logons’ is set

It specifies the location of a user’s home directory (from the client

point of view)

; logon drive = H:

logon home = \%N%U

The following setting only takes effect if ‘domain logons’ is set

It specifies the script to run during logon. The script must be stored

in the [netlogon] share

NOTE: Must be store in ‘DOS’ file format convention

; logon script = logon.cmd

This allows Unix users to be created on the domain controller via the SAMR

RPC pipe. The example command creates a user account with a disabled Unix

password; please adapt to your needs

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos “” %u

This allows machine accounts to be created on the domain controller via the

SAMR RPC pipe.

The following assumes a “machines” group exists on the system

; add machine script = /usr/sbin/useradd -g machines -c “%u machine account” -d /var/lib/samba -s /bin/false %u

This allows Unix groups to be created on the domain controller via the SAMR

RPC pipe.

; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

If you want to automatically load your printer list rather

than setting them up individually then you’ll need this

load printers = yes

lpr(ng) printing. You may wish to override the location of the

printcap file

; printing = bsd
; printcap name = /etc/printcap

CUPS printing. See also the cupsaddsmb(8) manpage in the

cupsys-client package.

; printing = cups
; printcap name = cups

############ Misc ############

Using the following line enables you to customise your configuration

on a per machine basis. The %m gets replaced with the netbios name

of the machine that is connecting

; include = /home/samba/etc/smb.conf.%m
include = /etc/samba/shares.conf
include = /etc/samba/shares_email.conf

Most people will find that this option gives better performance.

See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html

for details

You may want to add the following on a Linux system:

SO_RCVBUF=8192 SO_SNDBUF=8192

socket options = TCP_NODELAY

The following parameter is useful only if you have the linpopup package

installed. The samba maintainer and the linpopup maintainer are

working to ease installation and configuration of linpopup and samba.

; message command = /bin/sh -c ‘/usr/bin/linpopup “%f” “%m” %s; rm %s’ &

Domain Master specifies Samba to be the Domain Master Browser. If this

machine will be configured as a BDC (a secondary logon server), you

must set this to ‘no’; otherwise, the default behavior is recommended.

domain master = auto

Some defaults for winbind (make sure you’re not using the ranges

for something else.)

idmap config * : backend = tdb
idmap config * : range = 10000-20000
idmap config TATA : backend = ad
idmap config TATA : schema_mode = rfc2307
idmap config TATA : range = 20001-40000
template shell = /bin/bash

The following was the default behaviour in sarge,

but samba upstream reverted the default because it might induce

performance issues in large organizations.

See Debian bug #368251 for some of the consequences of not

having this setting and smb.conf(5) for details.

winbind enum groups = yes
winbind enum users = yes
winbind use default domain = Yes

Setup usershare options to enable non-root users to share folders

with the net usershare command.

Maximum number of usershare. 0 (default) means that usershare is disabled.

; usershare max shares = 100

Allow users who’ve been granted usershare privileges to create

public shares, not just authenticated ones

; usershare allow guests = yes

[/code]

Cordialement.

#9

Updated – 20/12/2012.