Windows 10에서 Samba 공유를 볼 수 없음


0

Ubuntu 서버 14.04.5 (Trusty Tahr) 및 Samba 4.3.11을 실행하는 NAS 서버가 있습니다. 솔직히 말해서 저는 Samba의 모든 복잡성을 모릅니다. YouTube 동영상 몇 개를 보면서 NAS를 설정했습니다.

나는 약간의 연구를 해왔고 Windows 10이 SMBV 3.11을 사용하기 때문에 공유를 볼 수 없지만 Samba에서 4.3 버전부터 수정 될 것이라고 읽었습니다.

Windows 7 컴퓨터 4 대, OpenELEC를 실행하는 2 개의 Raspberry Pis, OpenELEC를 실행하는 2 개의 HTPC, 5 개의 Android 장치 및 Windows 10 랩탑이 있습니다. Windows 10 컴퓨터 (빌드 1607)를 제외한 모든 컴퓨터에서 공유 폴더를 볼 수 있습니다.

인터넷 검색에서 제안한대로 Windows 10에서 SMBv1을 켜려고했지만 작동하지 않았습니다. 왜 주식을 볼 수 없습니까?

Samba에 설정 문제가 있다고 가정합니다 (Windows 10 컴퓨터의 모든 Windows 7 컴퓨터를 볼 수 있으며 그 반대도 마찬가지입니다).

공유에 두 번 연결할 수있었습니다. 첫 번째는 기계를 받았을 때였습니다. NAS의 이더넷 케이블을 변경해야 할 때 최근에 다시 연결되었습니다. 네트워크에 표시되지 않지만 Windows 10 시스템에서 IP 주소를 핑 (Ping)하고 SSH를 통해 로그인하고 webmin을 통해 로그인 할 수 있습니다.

머리가 긁혔습니다. 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]
browseable = no
max log size = 1000
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
syslog = 0
workgroup = PHD
pam password change = yes
passwd program = /usr/bin/passwd %u
panic action = /usr/share/samba/panic-action %d
passdb backend = tdbsam
usershare allow guests = yes
os level = 20
wins support = true
load printers = no
server string = %h server (Samba, Ubuntu)
unix password sync = yes
dns proxy = no
obey pam restrictions = yes
log file = /var/log/samba/log.%m
server role = standalone server
map to guest = bad user
netbios name = NAS-DRIVE
available = no

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server

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

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

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

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

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


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

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.


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

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

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

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections

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

#======================= 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
[Films]
 comment = Films
 path = /home/paulnas/Raid/Films
 browseable = yes
 read only = no

[Films 2]
 comment = Films2
 path = /home/paulnas/Raid/Films2
 browseable = yes
 read only = no

[Kids Films]
 comment = Kids Films
 path = /home/paulnas/Raid/Kids_films
 browseable = yes
 read only = no

[Music]
 comment = Music
 path = /home/paulnas/Raid/Music
 browseable = yes
 read only = no

[Photos]
 comment = Photos
 path = home/paulnas/Raid/Photos
 browseable = yes
 read only = no

답변:


0

아마도 이것이 도움이 될 것입니다 :

  1. '관리자'로 Windows PowerShell을 실행하십시오.

  2. 다음 명령을 입력하십시오 :

    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
    sc.exe config mrxsmb20 start= disabled
    
  3. 재부팅

  4. 네트워크의 서버를 참조하십시오

출처 : 네트워크에서 우분투 서버를 발견하지 못했습니다


2
슈퍼 유저에 오신 것을 환영합니다. 당신의 대답은 더 자세한 내용 으로부터 유익을 얻을 수 있습니다 . 솔루션의 작동 방식 / OP 문제를 해결하는 방법을 설명하기 위해이를 편집하십시오. 특히, 이러한 SC명령 은 무엇 을하며 어떻게 문제를 해결합니까? 기여해 주셔서 감사합니다.
Twisty Impersonator

무엇을해야합니까? 보안 영향은 무엇입니까?
Peter Mortensen

명령에 대한 모든 추가 정보는 그가 제공 한 링크의 다른쪽에 있습니다. 누군가 Microsoft의 Technet에 대해 본질적으로 동일한 질문을했습니다.
Caine Kiewit
당사 사이트를 사용함과 동시에 당사의 쿠키 정책개인정보 보호정책을 읽고 이해하였음을 인정하는 것으로 간주합니다.
Licensed under cc by-sa 3.0 with attribution required.