Why does the first access to самба shared folder always fail?

I shared в folder with самба. Access is allowed only with username and password. If I try to access from Windows or Android, I always get в failure on the first try and в success from the second on.

This is my / и т.д. / самба / 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 <<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 ###########

#
# 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

This is /var/log/samba/log.smdb : http://pastebin.com/W30hmKnQ

Here you пахал with в log from the first failed attempt:

[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

User permissions:

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
3
задан 15 October 2015 в 16:14

4 ответа

Единственная разница I видит, в глобальной конфигурации, между smb.conf, который я имею на своем рабочем столе (который хорошо работает), и Ваша конфигурация, line:-

username map = /etc/samba/smbusers

, Таким образом, мой вопрос - Вы, нуждаются в нем? Файл правилен? Вы соединяетесь с правильно нанесенным на карту пользователем?

, Что содержит/var/log/samba/? Обычно есть файл, названный согласно предпринятой связи. Вам необходимо найти причину, она уменьшила связь в одном из тех.

, Если Вы можете найти соответствующее сообщение регистрации, отправьте его в своем вопросе, если Вы не можете понять его

Update:-

, я проверил и по умолчанию уровень регистрации = 0, что означает, что оно не помещает большую часть использования в файлах системного журнала. Для ошибок идентификации нужен уровень регистрации 2, по крайней мере. Таким образом, я предлагаю, чтобы Вы попытались добавить

log level = 2

К [глобальному] разделу файла конфигурации выше (я поместил его в разделе Debugging/Accounting), и попробовать еще раз. Вы должны получить регистрацию файла. созданный, с IP клиентов, показывая, что, если кто-либо это пыталось соединиться как. Мое предположение, оно предпринимает начальную попытку как 'гостя', которого Ваше сетевое имя в конфигурации выше, не разрешает.

В моем тесте, с вышеупомянутой конфигурацией, я получаю following:-

[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

и

[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

, И для правильного логина я получаю following:-

[2015/10/15 12:44:32.343347,  2] ../source3/auth/auth.c:278(auth_check_ntlm_password)
  check_ntlm_password:  authentication for user [user1234] -> [user1234] -> [user1234] succeeded
[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=hostname1234, name type = 0

, Весь из который взятый от регистрации 127.0.0.1, используя

smbclient -L localhost -U <username>

хорошо, с непредусмотрительностью, Ваша регистрация включала этот line:-

[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

, бит getpwuid (4294967295) подведенный перечислен в https://bugzilla.samba.org/show_bug.cgi? id=10604 как проблема в самбе> версия 4.1.7, которой Это кажется, есть проблема с самбой (winbind) возвращение-1 (иначе 4294967295), когда это терпит неудачу к вещам поиска.
есть участок в Bugzilla (к источнику), или по-видимому изменение конфигурации, чтобы добавить

idmap config * : range = 1000-1999999 

Препятствует тому, чтобы winbind возвратил ошибку.

Все это кажется немного маловероятным, но их итоговые матчи Ваши, таким образом, это, вероятно, правильно.

4
ответ дан 1 December 2019 в 16:27

Что нужно сделать, чтобы уловить, что идет не так во время первого соединения.

  1. Повысьте уровень регистрации на мгновение до 3 или 5
  2. Добавьте Wireshark на вашем компьютере с Windows и прослушивайте сетевой трафик только между двумя IP-адресами (клиент и сервер) [ 113]
  3. Захватывайте пакеты и на стороне сервера, используя tcpdump

Я полагаю, что это связано с установлением соединения между клиентом и сервером перед этим. даже достигает точки аутентификации пользователя.

Вопрос: версия Samba? ОС Windows? ОС Linux? Дайте мне несколько цифр :-P

В этих журналах должно быть точно указано, что происходит. Опубликуйте важные части журналов здесь.

Если вам нужна помощь, загрузите журналы куда-нибудь и позвольте мне взглянуть.

Удачи!

0
ответ дан 1 December 2019 в 16:27

Я смог работать вокруг этой проблемы путем создания пользователя, отображающегося в smbusers от учетной записи кого-то до учетной записи Unix. В моем случае учетные записи имели то же имя, таким образом, мой smbusers похож:

# Unix_name = SMB_Name1 SMB_Name2 ...
root = administrator
nobody = guest smbguest pcguest
bobssmbact = bobsmbact  # add lines like these

Вносят изменение затем:

> service samba restart.

существует отчет об ошибках по этой проблеме здесь: https://bugzilla.samba.org/show_bug.cgi? id=10604

0
ответ дан 1 December 2019 в 16:27

Я не знаю, является ли это решением, но я начал настраивать Сервер Самбы, и во всех обучающих программах я видел, они все говорят, чтобы иметь security = user в [глобальном] определении. Это, как предполагается, как правило, прибывает, прокомментировал в .conf файле. Это не сделало для меня, таким образом, мне сказали добавить что, идеально ниже ###Authentication заголовка. Это может работать на Вас.

-1
ответ дан 1 December 2019 в 16:27

Другие вопросы по тегам:

Похожие вопросы: