Smb1 disabled no workgroup available linux

Windows 10 Share not accessible from Ubuntu 16.04 LTS

I am trying to connect/mount a point on my Ubuntu 16.04 LTS VM to a share on the host which is a Windows 10 with no success. The goal is so that I can download files on Ubuntu(VM) and transfer them to the Windows host. The Windows share is accessible from other windows hosts on the same network but not from the Ubuntu VM, even though there is network connectivity as I can ping(VM configured in «Bridged» mode). I have tried running:

sudo mount -t cifs -o username=username //ip_address/Windows_Share /mount/point/Ubuntu 

This comes back with an error indication that the host is down, which is not true since the share running on it can be accessed by other Windows boxes. I have read some posts about it and someone mentioned there is a conflict with the SMB version used by Ubuntu and Windows 10, which now disables SMB1. So they advised to run the below to check:

in addition to xguru’s configuration changes, consider running sudo testparm -s to test the validity of your smb.conf file.

2 Answers 2

Sounds like you are on the right track. If the problem is related to SMB1 the following will resolve your issue.

First make a copy of smb.conf

cp /etc/samba/smb.conf /etc/samba/smb.conf.orig 

sudo gedit /etc/samba/smb.conf 

Feel free to use vi/vim/nano if you do not prefer gedit

In the file, add the following in the [global] section

client min protocol = SMB2 client max protocol = SMB3 

After saving the edits to the file. Restart SMB

sudo service smbd restart 

If this does not work please include errors.

I have tried the configuration you’ve suggested and ran the below after restarting smbd and even did a full system reboot(just to make sure): smbclient -L -U -d SMB2 But still nothing: > Connection to failed (Error > NT_STATUS_RESOURCE_NAME_NOT_FOUND) NetBIOS over TCP disabled — no > workgroup available The battle continues. 🙂

I don’t seem to have a smbd here in debian stretch server: sudo service smbd restart => Failed to restart smbd.service: Unit smbd.service not found. 🙁 Changing smb.conf didn’t help but add -o vers=3.0, from the other other answer did.

Ok, sorry for coming back so late to this. The fix basically is this:

sudo mount -o vers=3.0,username=,uid=,gid=,forceuid,forcegid, /// ///

Note that I have skipped the «-t(—type)» option this time, since if this option is not specified «mount» will try and guess what system to use, and with all honesty, given the amount of reading I had already done on what was going on with Windows 10 sharing protocols, I chose to let «mount» do its magic for me. 😉

Here for an extract of the «mount man page»:

«If no -t option is given, or if the auto type is specified, mount will try to guess the desired type. Mount uses the blkid library for guessing the filesystem type; if that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems. All of the filesys‐tem types listed there will be tried, except for those that are labeled «nodev» (e.g., devpts, proc and nfs). If /etc/filesystems ends in a line with a single *, mount will read /proc/filesystems afterwards. While trying, all filesystem types will be mounted with the mount option silent.»

Also, since «mount» could only be run as root, but other programs writing to this mount point aren’t run as root, you will need to specify the user and group which you want to grant writing privileges(ownership) to the mount location, hence the use of: uid=,gid=,forceuid,forcegid, .

Done! @xguru, Thanks for the help!:)

Источник

Samba Configuration on RHEL 8.2: SMB1 disabled — no workgroup available

I’ve been taking a crack at configuring Samba to allow my Guest OS (RHEL 8.2), running on Oracle VM VirtualBox 6.1.8, to talk to my Host OS (Win10) following this guide here. Unfortunately, using a Shared Folder via Guest Additions does not provide the dev environment that is required. So upon running:
# smbclient -U -L localhost
I get the following:

Enter WORKGROUP\'s password: Sharename Type Comment --------- ---- ------- athena Disk ATHENA Server # my desired share, mapped to root IPC$ IPC IPC Service (Samba 4.11.2) Disk Home Directories SMB1 disabled -- no workgroup available 

I believe that this error: SMB1 disabled — no workgroup available is blocking my Host OS’ ability to detect the share on the network via the VM Box’s IP So far my google-fu has turned up no pertinent results, so any insights would be appreciated Relevant Configuration Info (What I think is at least):
testparm Passes

Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed Server role: ROLE_STANDALONE 

# See smb.conf.example for a more detailed config file or # read the smb.conf manpage. # Run 'testparm' to verify the config is correct after # you modified it. [global] workgroup = WORKGROUP protocol = SMB3 security = user map to guest = bad user guest ok = yes netbios name = athena_server passdb backend = tdbsam log file = /var/log/samba/%m.log log level = 1 [homes] comment = Home Directories valid users = %S, %D%w%S browseable = no read only = no inherit acls = yes [athena] comment = ATHENA Server path = / valid users = browseable = yes public = yes writable = yes #[printers] # comment = All Printers # path = /var/tmp # printable = Yes # create mask = 0600 # browseable = No #[print$] # comment = Printer Drivers # path = /var/lib/samba/drivers # write list = @printadmin root # force group = @printadmin # create mask = 0664 # directory mask = 0775 

SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 31 

samba_create_home_dirs (on , on) Allow samba to create home dirs samba_domain_controller (on , on) Allow samba to domain controller samba_enable_home_dirs (on , on) Allow samba to enable home dirs samba_export_all_ro (on , on) Allow samba to export all ro samba_export_all_rw (on , on) Allow samba to export all rw samba_load_libgfapi (on , on) Allow samba to load libgfapi samba_portmapper (on , on) Allow samba to portmapper samba_run_unconfined (on , on) Allow samba to run unconfined samba_share_fusefs (on , on) Allow samba to share fusefs samba_share_nfs (on , on) Allow samba to share nfs sanlock_use_samba (on , on) Allow sanlock to use samba tmpreaper_use_samba (on , on) Allow tmpreaper to use samba use_samba_home_dirs (on , on) Allow use to samba home dirs virt_use_samba (on , on) Allow virt to use samba 

Источник

Smb1 disabled no workgroup available linux

Подключение Linux Mint 19.1 (192.168.4.1 enp4s0) к Win7 (192.168.4.2) через витую пару мать-в-мать.
С винды я захожу в папки линя — тут всё хорошо. А вот обратное направление не работает.

smbclient -L 192.168.4.2 Enter WORKGROUPE\name's password: Sharename Type Comment --------- ---- ------- ADMIN$ Disk Удаленный Admin C$ Disk Стандартный общий ресурс D$ Disk Стандартный общий ресурс IPC$ IPC Удаленный IPC Users Disk Архив Disk Обмен Disk Reconnecting with SMB1 for workgroup listing. Connection to 192.168.4.2 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND) Failed to connect with SMB1 -- no workgroup available 

enp3s0: flags=4163 mtu 1500 inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.5.255 inet6 fe80::faaa:9f73:dd17:5b2f prefixlen 64 scopeid 0x20 ether 00:1e:58:af:89:70 txqueuelen 1000 (Ethernet) RX packets 593900 bytes 164948348 (164.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 627345 bytes 459250952 (459.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp4s0: flags=4163 mtu 1500 inet 192.168.4.1 netmask 255.255.0.0 broadcast 192.168.255.255 inet6 fe80::2dd5:a5f5:cb09:e784 prefixlen 64 scopeid 0x20 ether 70:8b:cd:9d:eb:32 txqueuelen 1000 (Ethernet) RX packets 1208 bytes 164935 (164.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 440 bytes 78690 (78.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Локальная петля (Loopback)) RX packets 1219 bytes 124964 (124.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1219 bytes 124964 (124.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

WORKGROUPE \\S1 Lin server (Samba, Ubuntu) \\S1\IPC$ IPC Service (Sams24 server (Samba, Ubuntu)) \\S1\Toshiba_share Full Share \\S1\Share2 Full Share WORKGROUP \\ÆâÉ

Network: Device-1: VIA VT6105/VT6106S [Rhine-III] vendor: D-Link System DFE-520TX Fast PCI driver: via-rhine v: N/A port: e000 bus ID: 03:00.0 IF: enp3s0 state: unknown speed: 100 Mbps duplex: full mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: 2.3LK-NAPI port: d000 bus ID: 04:00.0 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac:

[global] workgroup = workgroupe netbios name = s1 server string = %h server (Samba, Ubuntu) ; dns proxy = yes log file = /var/log/samba/log.%m max log size = 1000 map to guest = bad user usershare allow guests = yes username map = /etc/samba/smbusers security = user ; encrypt passwords = yes guest ok = yes guest account = name name resolve order = bcast lmhosts host wins local master = Yes interfaces = 127.0.0.0/8 enp4s0 bind interfaces only = true

В винде:
В хосте добавлена строка с IP ПК с линуксом.
В свойствах расшариваемой на винде папки «Обмен» добавлен пользователь Гость и во вкладки «Доступ «и «Безопасность».
Общий доступ с парольной защитой отключен.
В локальных политиках «Отказать в доступе этому компьютеру из сети» — пусто.
. gpedit.msc — Конфигурация компьютера — Конфигурация Windows — Параметры безопасности — Локальные политики — Параметры безопасности.
Там есть 2 параметра:
Отключено «Сетевой доступ: запретить анонимный доступ к именованным каналам и общим ресурсам»
Включено «Сетевой доступ: разрешать применение разрешений «Для всех» к анонимным пользователям»

В немо по запросу в адресной строке «smb://192.168.4.2/» получаю:

Текущая:
KDE Neon 5.2x
Предыдущая:
Linux Mint 19.1 Cinnamon
Железо:
Intel Core i3-6100 CPU @ 3.7 ГГц x2, 16Гб ОЗУ

Источник