"Other Locations" does not automatically find Samba servers in Ubuntu 18.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dolphin |
Unknown
|
High
|
|||
gvfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
samba (Ubuntu) |
Invalid
|
High
|
Unassigned |
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-
Apr 27 13:49:34 david-HP-
Apr 27 13:49:35 david-HP-
Apr 27 13:49:35 david-HP-
Apr 27 13:49:35 david-HP-
Apr 27 13:49:35 david-HP-
Apr 27 13:49:35 david-HP-
Apr 27 13:49:40 david-HP-
description: | updated |
description: | updated |
summary: |
- "Windows Network" does not find Samba servers in Ubuntu 18.04 + "Other Locations" do not automatically find Samba servers in Ubuntu + 18.04 |
summary: |
- "Other Locations" do not automatically find Samba servers in Ubuntu + "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 |
Changed in gvfs: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in nautilus: | |
importance: | Unknown → High |
affects: | nautilus → dolphin |
Changed in gvfs: | |
status: | Confirmed → Fix Released |
Changed in samba (Ubuntu): | |
status: | Confirmed → Invalid |
importance: | Undecided → High |
no longer affects: | oem-priority |
affects: | samba → ubuntu |
Changed in ubuntu: | |
importance: | Unknown → Undecided |
status: | Unknown → New |
no longer affects: | ubuntu |
affects: | gvfs → ubuntu |
Changed in ubuntu: | |
importance: | Medium → Undecided |
status: | Fix Released → New |
no longer affects: | ubuntu |
Dolphin doesn't show any samba share.
smb:// and smb://workgroup/ are empty.
However, smbtree is always working.
If made all test with deactivated firewall.
Entering a specific share like smb://twvm1/ is always working.
I've made many test with different distributions and software versions:
--------
DOES NOT WORK:
Tumbleweed with:
Plasma: 5.12.3
Framework: 5.44.0
Applications: 17.12.3
Samba: 4.7.6
Fedora 27 with
Plasma: 5.12.2
Framework: 5.44.0
Applications: 17.12.2
Samba: 4.7.6
Neon with
Plasma: 5.12.3
Framework: 5.44.0
Applications: 17.12.3
Samba 4.3.11-Ubuntu
extra file: ~/.smb/smb.conf
[global]
client max protocol = SMB2
----------
WORKS:
Neon with
Plasma: 5.12.3
Framework: 5.44.0
Applications: 17.12.3
Samba 4.3.11-Ubuntu
Tumbleweed with:
Plasma: 5.12.3
Framework: 5.44.0
Applications: 17.12.3
Samba: 4.6.16 (Downgraded with repo home:j-engel)
Tumbleweed with:
Plasma: 5.12.3
Framework: 5.44.0
Applications: 17.12.3
Samba: 4.7.6
extra file: ~/.smb/smb.conf
[global]
client max protocol = NT1
===============
Conclusion:
As soon as the samba protocol newer NT1 (e.g. SMB2) is used, then dolphin doesn't show the samba shares.
You can force the usage of NT1 via:
- Samba < 4.7
or adding the extra file ~/.smb/smb.conf
[global]
client max protocol = NT1
You can force the usage of SMB2 or SMB3 via:
- Samba >= 4.7
or adding the extra file ~/.smb/smb.conf
[global]
client max protocol = SMB3