Defaults for xenial (samba 4.3.11):
client min protocol = CORE
client max protocol = default (which is NT1 in this version of samba)
Defaults for artful (samba 4.6.7):
client min protocol = CORE
client max protocol = default (which is NT1 in this version of samba)
Defaults for bionic (samba 4.7.6):
client min protocol = CORE
client max protocol = default (which is SMB3_11 in this version of samba)
So before bionic, if you wanted a more secure protocol, you had to
specify it (like smbclient's -m SMB3 option).
Now in bionic, if you want a *less* secure protocol. you have to specify
it.
Ideally, computer browsing and actually connecting to shares should
happen with different protocol versions.
smbclient in bionic does a quick downgrade to NT1 when needed. Notice the
"Reconnecting" message intertwined in the output below:
ubuntu@bionic-desktop:~$ smbclient -L xenial -N -m SMB3
Anonymous login successful
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
public Disk Public share
IPC$ IPC IPC Service (xenial-desktop server (Samba,
Ubuntu))
Reconnecting with SMB1 for workgroup listing.
Anonymous login successful
Server Comment
--------- -------
Workgroup Master
--------- -------
UBUNTU XENIAL
In artful, that downgrade does not happen, and we don't get the workgroup
listing:
ubuntu@artful-desktop:~$ smbclient -L xenial -N -m SMB3
Anonymous login successful
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
public Disk Public share
IPC$ IPC IPC Service (xenial-desktop server (Samba,
Ubuntu))
Anonymous login successful
Server Comment
--------- -------
Workgroup Master
--------- -------
ubuntu@artful-desktop:~$
I suspect smbtree does the same. In bionic, where max protocol is SMB3_11 by
default, it works out of the box. But in artful, if I set client max protocol
to SMB3_11, it stops working:
ubuntu@artful-desktop:~$ testparm -s -v 2>/dev/null|grep "client max protocol"
client max protocol = default
ubuntu@artful-desktop:~$ smbtree
UBUNTU
\\XENIAL xenial-desktop server (Samba, Ubuntu)
\\XENIAL\IPC$ IPC Service (xenial-desktop
server (Samba, Ubuntu))
\\XENIAL\public Public share
\\XENIAL\print$ Printer Drivers
\\BIONIC bionic-desktop server (Samba, Ubuntu)
\\BIONIC\IPC$ IPC Service (bionic-desktop
server (Samba, Ubuntu))
\\BIONIC\public Public share
\\BIONIC\print$ Printer Drivers
\\ARTFUL artful-desktop server (Samba, Ubuntu)
\\ARTFUL\IPC$ IPC Service (artful-desktop
server (Samba, Ubuntu))
\\ARTFUL\public Public share
\\ARTFUL\print$ Printer Drivers
ubuntu@artful-desktop:~$ sudo vi /etc/samba/smb.conf
ubuntu@artful-desktop:~$ testparm -s -v 2>/dev/null|grep "client max protocol"
client max protocol = SMB3
ubuntu@artful-desktop:~$ smbtree
ubuntu@artful-desktop:~$
So in summay, bionic samba's own tools seem to know when NT1 is needed and
downgrade appropriately. Ideally the rest of the smb ecosystem should do the
same, assuming there is no way to get the computer listing with non-NT1
protocols.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1767454
Title:
"Other Locations" does not automatically find Samba servers in Ubuntu
18.04
Status in gvfs:
Confirmed
Status in samba:
Unknown
Status in nautilus package in Ubuntu:
New
Status in samba package in Ubuntu:
New
Bug description:
Ubuntu: 18.04 clean install
Nautilus: 1:3.26.3-0ubuntu4
The actions taken to produce the problem:
Click on “Other Locations” in Nautilus.
The expected result of these actions:
Samba servers to automatically show up under “Networks”. This is the behavior
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows
Network” immediately shows "Folder is Empty".
The actual result of these actions:
The Samba servers never show up under “Networks” and clicking on "Windows
Network" always immediately comes up with "Folder is Empty".
Further information:
This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu
17.10 machines still work like expected.
I can still manually type in the Samba information in "Connect to
Server" and the 18.04 machines connect just fine.
From syslog:
Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13'
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000
pid=1333] Successfully activated service 'org.gnome.Nautilus'
Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating
via systemd: service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname
Service...
Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare
info" but it failed: Failed to execute child process “net” (No such file or
directory)
Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system]
Successfully activated service 'org.freedesktop.hostname1'
Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on
directory /var/cache/samba: Permission denied
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
