再问:20.04无法访问无线路由器上的U盘

包含网卡/无线网的网络问题和ADSL/校园网/宽带拨号支持及代理/共享等网络使用问题
头像
男菜鸟
帖子: 1366
注册时间: 2008-12-16 14:01
来自: 漂在江湖

再问:20.04无法访问无线路由器上的U盘

#1

帖子 男菜鸟 » 2020-05-01 10:53

原帖子:
viewtopic.php?f=116&t=491015

按照版主提示:在[global]里面加上client min protocol = CORE,后可以进入U盘,
但是所有文件都是“文件夹”的图标,而且无法打开文件,求助解决!
图1
图1
图2
图2
头像
男菜鸟
帖子: 1366
注册时间: 2008-12-16 14:01
来自: 漂在江湖

Re: 再问:20.04无法访问无线路由器上的U盘

#3

帖子 男菜鸟 » 2020-05-01 17:15

[global]
workgroup = HOME
security = user
client min protocol = CORE

usershare path = /var/lib/samba/usershares
usershare max shares = 100
usershare allow guests = yes
usershare owner only = yes
wins support = no
homtoo
帖子: 313
注册时间: 2006-12-06 11:52
联系:

Re: 再问:20.04无法访问无线路由器上的U盘

#4

帖子 homtoo » 2020-05-01 17:18

你看看https://devanswers.co/discover-ubuntu-machines-samba-shares-windows-10-network/说的方法可行不?
Installing WDS on Ubuntu

wsdd implements a Web Service Discovery host daemon for Ubuntu. This enables (Samba) hosts to be found by Web Service Discovery Clients like Windows. Read more at: https://github.com/christgau/wsdd

Download and unzip the archive.

wget https://github.com/christgau/wsdd/archive/master.zip

unzip master.zip

Move wsdd.py.

sudo mv wsdd-master/src/wsdd.py wsdd-master/src/wsdd

Copy to /usr/bin.

sudo cp wsdd-master/src/wsdd /usr/bin

Copy service to /etc/systemd/system.

sudo cp wsdd-master/etc/systemd/wsdd.service /etc/systemd/system

Open wsdd.service in nano and replace After=network-online.target with After=network.target network-online.target multi-user.target

Also comment out User=nobody and Group=nobody with a ; semicolon.

sudo nano /etc/systemd/system/wsdd.service

/etc/systemd/system/wsdd.service

[Unit]
Description=Web Services Dynamic Discovery host daemon
; Start after the network has been configured
After=network.target network-online.target multi-user.target
Wants=network-online.target
; It makes sense to have Samba running when wsdd starts, but is not required
;Wants=smb.service

[Service]
Type=simple
ExecStart=/usr/bin/wsdd --shortlog
; Replace those with an unprivledged user/group that matches your environment,
; like nobody/nogroup or daemon:daemon or a dedicated user for wsdd
;User=nobody
;Group=nobody
; The following lines can be used for a chroot execution of wsdd.
; Also append '--chroot /run/wsdd/chroot' to ExecStart to enable chrooting
;AmbientCapabilities=CAP_SYS_CHROOT
;ExecStartPre=/usr/bin/install -d -o nobody -g nobody -m 0700 /run/wsdd/chroot
;ExecStopPost=rmdir /run/wsdd/chroot

[Install]
WantedBy=multi-user.target

Save and exit (press CTRL + X, press Y and then press ENTER)

Reload daemon.

sudo systemctl daemon-reload

Start and enable wsdd.

sudo systemctl start wsdd

sudo systemctl enable wsdd

Output:

Created symlink /etc/systemd/system/multi-user.target.wants/wsdd.service → /etc/systemd/system/wsdd.service.

Now check that the service is running.

sudo service wsdd status

Output:

● wsdd.service - Web Services Dynamic Discovery host daemon
Loaded: loaded (/etc/systemd/system/wsdd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-03-09 13:43:04 CET; 1h 48min ago
Main PID: 11976 (python3)
Tasks: 1 (limit: 6662)
Memory: 10.8M
CGroup: /system.slice/wsdd.service
└─11976 python3 /usr/bin/wsdd --shortlog

mar 09 13:43:04 bb-srv1 systemd[1]: Started Web Services Dynamic Discovery host daemon.
mar 09 13:43:04 bb-srv1 wsdd[11976]: WARNING: no interface given, using all interfaces

As long as Windows 10 is set up correctly, you should now be able to browse your Ubuntu machines and Samba shares in the Windows file explorer. You may need to restart the Windows 10 machines to force discovery.
xenomorph0525
帖子: 526
注册时间: 2009-11-21 20:29

Re: 再问:20.04无法访问无线路由器上的U盘

#5

帖子 xenomorph0525 » 2020-05-01 18:10

男菜鸟 写了: 2020-05-01 17:15 [global]
workgroup = HOME
security = user
client min protocol = CORE

usershare path = /var/lib/samba/usershares
usershare max shares = 100
usershare allow guests = yes
usershare owner only = yes
wins support = no
在終端機
sudo apt install samba-common
sudo cp /usr/share/doc/samba-common/examples/smb.conf.default /etc/samba/smb.conf
sudo nano /etc/samba/smb.conf

在 [global] 的下一行插入下面這一行:
client min protocol = CORE

然後按 Ctrl+o 儲存,按 Ctrl+x 離開,接著重開機即可。
homtoo
帖子: 313
注册时间: 2006-12-06 11:52
联系:

Re: 再问:20.04无法访问无线路由器上的U盘

#6

帖子 homtoo » 2020-05-01 22:23

xenomorph0525 写了: 2020-05-01 18:10
男菜鸟 写了: 2020-05-01 17:15 [global]
workgroup = HOME
security = user
client min protocol = CORE

usershare path = /var/lib/samba/usershares
usershare max shares = 100
usershare allow guests = yes
usershare owner only = yes
wins support = no
在終端機
sudo apt install samba-common
sudo cp /usr/share/doc/samba-common/examples/smb.conf.default /etc/samba/smb.conf
sudo nano /etc/samba/smb.conf

在 [global] 的下一行插入下面這一行:
client min protocol = CORE

然後按 Ctrl+o 儲存,按 Ctrl+x 離開,接著重開機即可。
这样做了照样不行。
2020-05-01 22-21-40屏幕截图.png
头像
男菜鸟
帖子: 1366
注册时间: 2008-12-16 14:01
来自: 漂在江湖

Re: 再问:20.04无法访问无线路由器上的U盘

#7

帖子 男菜鸟 » 2020-05-01 22:40

是的,我操作的结果也一样 :Cry
homtoo
帖子: 313
注册时间: 2006-12-06 11:52
联系:

Re: 再问:20.04无法访问无线路由器上的U盘

#8

帖子 homtoo » 2020-05-02 8:57

男菜鸟 写了: 2020-05-01 22:40 是的,我操作的结果也一样 :Cry
你如果不怕重装系统可以试着安装wds,我觉得应该是正解。我是这段时间工作紧,不能有时间重装,不敢试。大家都弃用samba1,可是不是所有设备都能升级到samba2或3,应该要有个解决办法。或者应该提示风险,让使用者选择继续使用samba1的。
头像
astolia
论坛版主
帖子: 6570
注册时间: 2008-09-18 13:11

Re: 再问:20.04无法访问无线路由器上的U盘

#9

帖子 astolia » 2020-05-02 20:53

男菜鸟 写了: 2020-05-01 22:40 是的,我操作的结果也一样 :Cry
运行下面的命令

代码: 全选

sudo apt install smbclient
smbclient -m NT1 -c ls '\\192.168.50.1\doc'
把结果发上来
homtoo
帖子: 313
注册时间: 2006-12-06 11:52
联系:

Re: 再问:20.04无法访问无线路由器上的U盘

#10

帖子 homtoo » 2020-05-02 22:46

astolia 写了: 2020-05-02 20:53
男菜鸟 写了: 2020-05-01 22:40 是的,我操作的结果也一样 :Cry
运行下面的命令

代码: 全选

sudo apt install smbclient
smbclient -m NT1 -c ls '\\192.168.50.1\doc'
把结果发上来
homtoo@homtoo:~$ sudo apt install smbclient
[sudo] homtoo 的密码:
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
建议安装:
cifs-utils heimdal-clients
下列【新】软件包将被安装:
smbclient
升级了 0 个软件包,新安装了 1 个软件包,要卸载 0 个软件包,有 0 个软件包未被升级。
需要下载 366 kB 的归档。
解压缩后会消耗 1,857 kB 的额外空间。
获取:1 http://mirrors.nju.edu.cn/ubuntu focal-updates/main amd64 smbclient amd64 2:4.11.6+dfsg-0ubuntu1.1 [366 kB]
已下载 366 kB,耗时 16秒 (23.3 kB/s)
正在选中未选择的软件包 smbclient。
(正在读取数据库 ... 系统当前共安装有 183877 个文件和目录。)
准备解压 .../smbclient_2%3a4.11.6+dfsg-0ubuntu1.1_amd64.deb ...
正在解压 smbclient (2:4.11.6+dfsg-0ubuntu1.1) ...
正在设置 smbclient (2:4.11.6+dfsg-0ubuntu1.1) ...
正在处理用于 man-db (2.9.1-1) 的触发器 ...
homtoo@homtoo:~$ smbclient -m NT1 -c ls '\\192.168.50.1\doc'
do_connect: Connection to 192.168.50.1 failed (Error NT_STATUS_IO_TIMEOUT)
头像
男菜鸟
帖子: 1366
注册时间: 2008-12-16 14:01
来自: 漂在江湖

Re: 再问:20.04无法访问无线路由器上的U盘

#11

帖子 男菜鸟 » 2020-05-03 0:14

gu@gu-Inspiron-N311z:/etc/samba$ sudo apt install smbclient
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
建议安装:
cifs-utils heimdal-clients
下列【新】软件包将被安装:
smbclient
升级了 0 个软件包,新安装了 1 个软件包,要卸载 0 个软件包,有 0 个软件包未被升级。
需要下载 366 kB 的归档。
解压缩后会消耗 1,857 kB 的额外空间。
获取:1 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main amd64 smbclient amd64 2:4.11.6+dfsg-0ubuntu1.1 [366 kB]
已下载 366 kB,耗时 1秒 (495 kB/s)
正在选中未选择的软件包 smbclient。
(正在读取数据库 ... 系统当前共安装有 203066 个文件和目录。)
准备解压 .../smbclient_2%3a4.11.6+dfsg-0ubuntu1.1_amd64.deb ...
正在解压 smbclient (2:4.11.6+dfsg-0ubuntu1.1) ...
正在设置 smbclient (2:4.11.6+dfsg-0ubuntu1.1) ...
正在处理用于 man-db (2.9.1-1) 的触发器 ...
gu@gu-Inspiron-N311z:/etc/samba$ smbclient -m NT1 -c ls '\\192.168.50.1\doc'
Enter WORKGROUP\gu's password:
Server requested LANMAN password (share-level security) but 'client lanman auth = no' or 'client ntlmv2 auth = yes'
tree connect failed: NT_STATUS_ACCESS_DENIED
gu@gu-Inspiron-N311z:/etc/samba$
头像
astolia
论坛版主
帖子: 6570
注册时间: 2008-09-18 13:11

Re: 再问:20.04无法访问无线路由器上的U盘

#12

帖子 astolia » 2020-05-03 0:30

男菜鸟 写了: 2020-05-03 0:14 gu@gu-Inspiron-N311z:/etc/samba$ smbclient -m NT1 -c ls '\\192.168.50.1\doc'
Enter WORKGROUP\gu's password:
Server requested LANMAN password (share-level security) but 'client lanman auth = no' or 'client ntlmv2 auth = yes'
tree connect failed: NT_STATUS_ACCESS_DENIED
gu@gu-Inspiron-N311z:/etc/samba$

换这个试试

代码: 全选

smbclient -m NT1 --option='client min protocol=NT1' -N -c ls '\\192.168.50.1\doc'
如果你在文件管理器里访问路由器u盘需要输入特定的用户名,那么添加一个用户名参数

代码: 全选

smbclient -m NT1 --option='client min protocol=NT1' -U 用户名 -c ls '\\192.168.50.1\doc'
头像
astolia
论坛版主
帖子: 6570
注册时间: 2008-09-18 13:11

Re: 再问:20.04无法访问无线路由器上的U盘

#13

帖子 astolia » 2020-05-03 0:34

homtoo 写了: 2020-05-02 22:46 homtoo@homtoo:~$ smbclient -m NT1 -c ls '\\192.168.50.1\doc'
do_connect: Connection to 192.168.50.1 failed (Error NT_STATUS_IO_TIMEOUT)
这个和你的没关系。而且192.168.50.1是楼主的路由器地址,你生搬硬套干什么。就算要用这个,也该把ip和路径换成你的电脑的
homtoo 写了: 2020-05-02 8:57 你如果不怕重装系统可以试着安装wds,我觉得应该是正解。
肯定和wds没关系。你以前用18.04和19.10的时候,一样没有wds啊。
homtoo 写了: 2020-05-02 8:57 大家都弃用samba1,可是不是所有设备都能升级到samba2或3,应该要有个解决办法。或者应该提示风险,让使用者选择继续使用samba1的。
解决办法就是改smb.conf允许它使用低版本协议。把你整个smb.conf文件发上来,看看其他地方有没有需要设置的
homtoo
帖子: 313
注册时间: 2006-12-06 11:52
联系:

Re: 再问:20.04无法访问无线路由器上的U盘

#14

帖子 homtoo » 2020-05-03 10:21

对IP也觉得奇怪,但不懂就没想那么多。
我花半小时换回19.10了。
2020-05-03 10-18-26屏幕截图.png
这是19.10的samba.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)

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

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file

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

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 config * : backend = tdb
; idmap config * : range = 3000-7999
; idmap config YOURDOMAINHERE : backend = tdb
; idmap config YOURDOMAINHERE : range = 100000-999999
; 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 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

#======================= 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
头像
男菜鸟
帖子: 1366
注册时间: 2008-12-16 14:01
来自: 漂在江湖

Re: 再问:20.04无法访问无线路由器上的U盘

#15

帖子 男菜鸟 » 2020-05-03 22:23

gu@gu-Inspiron-N311z:~$ smbclient -m NT1 --option='client min protocol=NT1' -N -c ls '\\192.168.50.1\doc'
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
回复