Pourquoi le premier accès au dossier partagé Samba échoue-t-il toujours?
J'ai partagé un dossier avec Samba. L'accès est autorisé uniquement avec un nom d'utilisateur et un mot de passe. Si j'essaie d'accéder à partir de Windows ou d'Android, j'obtiens toujours un échec au premier essai et un succès à partir du deuxième.
Voici mon /etc/samba/smb.conf:
#
# 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.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# 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 = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
#### 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 #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "Active Directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
# 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 <<[email protected]> 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 ###########
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or '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
############ 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
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template Shell = /bin/bash
# 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
username map = /etc/samba/smbusers
#======================= Share Definitions =======================
# Un-comment the following (and Tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
; guest ok = no
; read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
; browseable = yes
; read only = yes
; guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
[Pubblici]
path = /home/mauro/Pubblici
writeable = yes
; browseable = yes
valid users = mauro
C'est /var/log/samba/log.smdb: http://Pastebin.com/W30hmKnQ
Vous êtes ici avec un journal de la première tentative infructueuse:
[2015/10/15 11:38:01.010825, 2] ../source3/param/loadparm.c:3582(do_section)
Processing section "[printers]"
[2015/10/15 11:38:01.011051, 2] ../source3/param/loadparm.c:3582(do_section)
Processing section "[print$]"
[2015/10/15 11:38:01.011139, 2] ../source3/param/loadparm.c:3582(do_section)
Processing section "[Pubblici]"
[2015/10/15 11:38:01.035299, 2] ../source3/auth/auth.c:278(auth_check_ntlm_password)
check_ntlm_password: authentication for user [mauro] -> [mauro] -> [mauro] succeeded
[2015/10/15 11:38:01.037346, 1] ../source3/auth/token_util.c:430(add_local_groups)
SID S-1-5-21-1432355103-2748604540-3142755518-1000 -> getpwuid(4294967295) failed
[2015/10/15 11:38:01.037433, 1] ../source3/smbd/sesssetup.c:276(reply_sesssetup_and_X_spnego)
Failed to generate session_info (user and group token) for session setup: NT_STATUS_UNSUCCESSFUL
Autorisations utilisateur:
Sudo pdbedit -L -v
---------------
Unix username: mauro
NT username:
Account Flags: [U ]
User SID: S-1-5-21-1432355103-2748604540-3142755518-1000
Primary Group SID: S-1-5-21-1432355103-2748604540-3142755518-513
Full Name: mauro
Home Directory: \\mauro-m14xr1\mauro
HomeDir Drive:
Logon Script:
Profile Path: \\mauro-m14xr1\mauro\profile
Domain: MAURO-M14XR1
Account desc:
Workstations:
Munged dial:
Logon time: 0
Logoff time: mer, 06 feb 2036 16:06:39 CET
Kickoff time: mer, 06 feb 2036 16:06:39 CET
Password last set: mar, 16 set 2014 14:13:30 CEST
Password can change: mar, 16 set 2014 14:13:30 CEST
Password must change: never
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
La seule différence que je peux voir, dans la configuration globale, entre le fichier smb.conf que j'ai sur mon bureau (qui fonctionne bien) et votre configuration, est la ligne suivante: -
username map = /etc/samba/smbusers
Donc, ma question est: en avez-vous besoin? Le fichier est-il correct? Vous connectez-vous avec l'utilisateur correctement mappé?
Que contient/var/log/samba /? Normalement, il existe un fichier nommé en fonction de la tentative de connexion. Vous devriez pouvoir trouver la raison pour laquelle il a refusé la connexion dans l'un de ceux-ci.
Si vous pouvez trouver le message de journal approprié, postez-le dans votre question, si vous ne pouvez pas le comprendre.
Mise à jour:-
J'ai vérifié et par défaut le niveau de journalisation = 0, ce qui signifie qu'il ne met pas beaucoup d'utilisation dans les fichiers journaux. Les erreurs d'authentification nécessitent un niveau de journalisation de 2 au moins. Donc, je vous suggère d'essayer d'ajouter
log level = 2
Vers la section [globale] du fichier de configuration ci-dessus (je le mets dans la section Débogage/Comptabilité), puis réessayez. Vous devriez obtenir un journal de fichier. créé, avec l’adresse IP du client, montrant ce qu’il a essayé de connacter le cas échéant. J'imagine qu'il s'agit d'une tentative initiale en tant qu'invité, ce que votre nom de partage dans la configuration ci-dessus ne permet pas.
Dans mon test, avec la configuration ci-dessus, j'obtiens ce qui suit: -
[2015/10/14 13:56:29.851320, 2] ../source3/auth/auth.c:288(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [guest] -> [guest] FAILED with error NT_STATUS_NO_SUCH_USER
et
[2015/10/14 13:51:12.307610, 2] ../source3/auth/auth.c:288(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [user1234] -> [user1234] FAILED with error NT_STATUS_WRONG_PASSWORD
Et pour une connexion correcte, je reçois ce qui suit: -
[2015/10/15 12: 44: 32.343347, 2] ../source3/auth/auth.c:278(auth_check_ntlm_password) Check_ntlm_password: authentification de l'utilisateur [utilisateur1234] -> [ user1234] -> [user1234] a réussi [2015/10/15 12: 44: 32.351284, 2] ../source3/smbd/reply.c:592(reply_special) netbios connect: name1 = LOCALHOST 0x20 name2 = HOSTNAME12340x0 [2015/10/15 12: 44: 32.351337, 2] ../source3/smbd/reply.c:633(reply_special) netbios connect: local = localhost remote = nomhôte1234, nom type = 0
Tiré de log.127.0.0.1 lors de l’utilisation de
smbclient -L localhost -U <username>
Ok, avec le recul, votre journal a inclus cette ligne: -
[2015/10/15 11: 38: 01.037346, 1] ../source3/auth/token_util.c:430(add_local_groups) SID S-1-5-21-1432355103- 2748604540-3142755518-1000 -> getpwuid (4294967295) a échoué
le bit getpwuid (4294967295) échoué est répertorié dans la liste https://bugzilla.samba.org/show_bug.cgi?id=10604 en tant que problème dans samba> version 4.1.7 Il semble qu'il y ait un problème avec samba (winbind) retournant -1 (alias 4294967295) lorsqu'il ne parvient pas à rechercher des éléments.
Il y a un correctif dans bugzilla (à la source) ou apparemment une modification de la configuration, à ajouter
idmap config * : range = 1000-1999999
Empêche winbind de renvoyer l'erreur.
Tout cela semble un peu improbable, mais leur résumé correspond au vôtre, donc c'est probablement exact.
Les choses à faire pour que vous puissiez capturer ce qui ne va pas lors de la première connexion.
- Augmenter momentanément le niveau de log à 3 ou 5
- Ajoutez Wireshark sur votre machine Windows et écoutez votre trafic réseau uniquement entre les deux adresses IP (client et serveur).
- Capturez également les paquets côté serveur en utilisant tcpdump
Je crois que c'est quelque chose qui a à voir avec l'établissement de la connexion entre le client et le serveur, avant même d'atteindre le point d'authentification de l'utilisateur.
Question: version Samba? Système d'exploitation Windows? OS Linux? Donnez-moi des chiffres :-P
Ces journaux devraient vous dire exactement ce qui se passe. Affichez les parties importantes des journaux ici.
Si vous avez besoin d’aide, téléchargez les journaux quelque part et donnez-moi un coup d’œil.
Bonne chance!
J'ai pu contourner ce problème en créant un mappage utilisateur dans smbusers du compte smb au compte unix. Dans mon cas, les comptes avaient le même nom, donc mes utilisateurs se présentent comme suit:
# Unix_name = SMB_Name1 SMB_Name2 ...
root = administrator
nobody = guest smbguest pcguest
bobssmbact = bobsmbact # add lines like these
Faites le changement alors:
> service samba restart.
Il existe un rapport de bogue sur ce problème ici: https://bugzilla.samba.org/show_bug.cgi?id=10604