Samba 공개 공유-Windows에서 암호를 계속 요청합니다 기타 포럼

이 Samba 공유를 올바르게 구성하는 방법을 알 수 없습니다. 실제로 무엇이 잘못되었는지 이해할 수 없습니다.

AskUbuntu 포럼, LinuxQuestions 및 기타 포럼 및 웹 사이트에서 많은 기사를 읽었습니다. 구성 매개 변수의 가능한 모든 조합을 실제로 시도했습니다.
나는 먼저 적절한 것들로 시도했다-그들이 일해야한다고 가정했던 것들-나는 지금까지 모든 매개 변수를 단계별로 변경하려고 시도했다. 도와주세요!

작동 방식

  • 2 주;
  • 1 공개 (서버에 연결 한 모든 사람이 액세스 가능, 읽기 / 쓰기), 1 보호 (정의 된 사용자 이름 및 비밀번호로만 액세스 가능, 읽기 / 쓰기);
  • 일부 사용자는 두 공유 (정의 된 공유)에 액세스해야하며 일부는 공개 공유에만 액세스 할 수 있어야합니다.
  • 공개 공유 이름 : DSMPubblica;
  • 개인 공유 이름 : DSMUfficio;
  • Windows에서는 문자 Y :에 DSMPubblica를 구성하고 바로 액세스 할 수 있어야하며 문자 Z :에 DSMUfficio를 구성 할 수 있어야하며 사용자 이름 및 비밀번호 창이 표시됩니다.

추가 노력과 로그 라인

나는 더 많은 것을 시도했다. 구성에서 두 개의 공유를 삭제하고 “Public”이라는 새로운 공용을 만들었습니다. 연결하려고하면 Windows에서 연결할 수 없다고 말합니다.

로그에서 볼 수 있습니다 :

  • smb_pwd_check_ntlmv1: incorrect password length (62)=> ??? 사용자에게 암호를 지정하지 말고 Windows에서 암호를 묻지도 않습니다 …
  • process_usershare_file: stat of /var/lib/samba/usershares/dsmufficio failed. Permission denied=> ??? 무엇입니까 /var/lib/samba/usershares/dsmufficio? 내 Linux 서버에 존재하지 않으며 구성 파일의 아무 곳에도 지정되어 있지 않습니다 ( “usershares”조차 포함되지 않음).

무슨 일이야

모든 것은 Windows 7 및 Windows 8.1에서 발생합니다.

  • 새 네트워크 공유를 연결하려고합니다.
  • DSMPubblica에 대해 문자 (Y :)를 선택합니다.
  • 서버 주소를 씁니다 (\ 10.10.10.1 \ DSMPubblica).
  • “다시 시작할 때 다시 연결”을 확인하고 “다른 자격 증명으로 연결”을 확인하지 않습니다.
  • 인증 창이 나타납니다!
  • 사용자 이름을 입력하지 않고 확인을 클릭하면 Windows에서 계속 진행할 수 없습니다. 사용자 이름과 암호가 필요합니다.
  • DSMUfficio에 대해 설정된 사용자 이름과 비밀번호를 제공하면 연결할 수 있습니다.
  • DSMUfficio의 경우와 동일하지만이 경우 Windows가 인증을 요청하는 것이 좋습니다.
  • “인증 자격 증명 저장”을 확인하면 다시 시작할 때 모든 것을 다시 묻습니다.

내 구성

주식

[DSMUfficio]
    delete readonly = yes
    writeable = yes
    path = /var/dsm/ufficio
    write list = tzanarella,jcangini,dlazzarato,mcazzoli,sgiombetti
    force group = dsm
    revalidate = yes
    comment = DSM share locale privata - solo autorizzati
    valid users = tzanarella,jcangini,dlazzarato,mcazzoli,sgiombetti
    create mode = 770
    directory mode = 770

[DSMPubblica]
    guest ok = yes
    guest account =
    writeable = yes
    delete readonly = yes
    path = /var/dsm/pubblica
    force directory mode = 777
    force create mode = 777
    comment = DSM share locale pubblica - senza restrizioni di accesso
    create mode = 777
    public = yes
    browsable = yes
    directory mode = 777

DSMPubblica 구성이 제대로 작동하기 위해 여러 번 변경되었습니다. 나는 모든 단일 조합을 실제로 시도했습니다 … 아무 효과가 없습니다. 더 많은 테스트, 정보, 사양이 필요하면 물어보고 알려주십시오. 감사합니다.

전체 구성

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

## Browsing/Identification ###

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

# 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 = w.x.y.z

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

# 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

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

# 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 uid = 10000-20000
;   idmap gid = 10000-20000
;   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

# 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

#======================= Share Definitions =======================

[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.
# The following parameter makes 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

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
#   cdrom share is accesed. For this to work /etc/fstab must contain
#   an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#   is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom


[DSMUfficio]
    delete readonly = yes
    writeable = yes
    path = /var/dsm/ufficio
    write list = tzanarella,jcangini,dlazzarato,mcazzoli,sgiombetti
    force group = dsm
    revalidate = yes
    comment = DSM share locale privata - solo autorizzati
    valid users = tzanarella,jcangini,dlazzarato,mcazzoli,sgiombetti
    create mode = 770
    directory mode = 770

[DSMPubblica]
    guest ok = yes
    guest account =
    writeable = yes
    delete readonly = yes
    path = /var/dsm/pubblica
    force directory mode = 777
    force create mode = 777
    comment = DSM share locale pubblica - senza restrizioni di accesso
    create mode = 777
    public = yes
    browsable = yes
    directory mode = 777



답변

익명으로 인증 된 동일한 호스트에 대한 인증을 지원하지 않는 Windows 7 및 이전 버전에 물린 것으로 생각합니다. Serverfault에서 이전답변을 보십시오 .


답변

이 문제를 해결하기 위해 [global] 섹션에서 설정하는 주요 옵션이었습니다.

손님에게 매핑 = 나쁜 사용자


답변

이것은 (최종적으로) 여기서 작동 한 구성입니다. 사용자 / 암호를 묻지 않고 Windows에서 Linux 서버에 액세스 할 수 있습니다.

[global]
workgroup = MYGROUP
server string = Samba Server %v
netbios name = debian
security = user
map to guest = bad user
dns proxy = no
#============= Share Definitions =================
[adriano]
force user = adriano
path = /home/adriano
browsable =yes
writable = yes
guest ok = yes
read only = no


답변

YouTube 비디오 에서 팁을 얻을 때까지 동일한 문제가 발생했습니다 (Windows는 pi의 암호를 계속 거부했습니다) . 기본적으로 명령을 실행해야했습니다.

sudo smbpasswd -a pi

pi samba 사용자를 생성합니다. Windows에서는 방금 RASPBERRYPI\pi사용자로 사용 하고 암호를 입력하면 작동합니다.


답변

2017, Ubuntu 17이 설치된 Windows 7

이 구성은 보안 또는 암호 프롬프트가 필요하지 않으므로 내부 개인 네트워크 또는 가상 PC (virtualbox, vmware 등)를위한 것입니다.

사용자 ‘david’의 예

우분투에서

sudo apt install samba

구성 편집

sudo nano /etc/samba/smb.conf

Windows의 내 PC에는 작업 그룹 : WORKGROUP이 있으므로 섹션을 전역으로 변경하지 않았 으며이 블록을 추가했습니다.

[Home Share]
comment = Home Public Folder
path = /home/david/projects
writable = yes
force user = david
public = no
browsable = yes

우분투에서 삼바에 사용자를 추가하고 암호를 만들어야합니다.

sudo smbpasswd -a david

서비스를 다시 시작

sudo systemctl restart smbd


답변

공유 할 보안 유형을 설정하십시오.

security = share

공개 공유에서 다음을 추가하십시오.

public = yes

더 많은 정보는 여기에서 찾을 수 있습니다 Samba servertype info


답변

비슷한 문제가 있었지만 클러스터 AD 컴퓨터 계정 암호가 만료되어 도메인에 다시 가입하여 작동하도록 발견했습니다.

이해가되는이 기사를 보았습니다.
https://access.redhat.com/discussions/1283873