Bug 1619719
| Summary: | Cannot browse SMB shares from GNOME after update to RHEL 7.5 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Skip Wyatt <awyatt> | |
| Component: | gvfs | Assignee: | Ondrej Holy <oholy> | |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.5 | CC: | amike, asn, awyatt, ayadav, bgollahe, gdeschner, jarrpa, jstephen, jwright, mboisver, oholy, tpelka | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | gvfs-1.36.2-3.el7 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1739116 (view as bug list) | Environment: | ||
| Last Closed: | 2019-08-06 12:57:59 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1650452, 1658690 | |||
| Bug Blocks: | 1656436, 1739116 | |||
|
Description
Skip Wyatt
2018-08-21 14:56:12 UTC
Can you please be more precise what this means? Do you mean that connecting to smb://server doesn't list the available shares? I've written a libsmbclient test to list shares and it works just fine. I've backported it to Samba 4.7 and it also works fine. So I wonder if the gvfs smb module works correctly. Looking at the upstream source code, it looks like they don't handle SMBC_FILE_SHARE in update_cache(). Ok, I think the issue is if you're trying to connect to a windows server which doesn't have SMB1 enabled or it has issues with the protocol selection. I suppose that this is related to the following Fedora issue: https://bugzilla.redhat.com/show_bug.cgi?id=1513394 Browsing over gvfs doesn't work unless "client max protocol = NT1" is used. I am convinced that smbtree and smbclient don't have this limitation, but there is no way to choose protocol version over libsmbclient... Andreas, When connecting using GNOME files connecting to smb://<servername> returns no shares. -Skip Ondrey, I've written several tests for Samba now. I've backported my test to Samba 4.7
$ grep "client min protocol" /etc/samba/smb.conf
client min protocol = SMB3
$ bin/smbtorture //addc/tmp -U'Administrator%Secret007!' --option=torture:smburl='smb://earth.milkyway.site' --option=clientminprotocol=SMB3 libsmbclient.list_shares
smbtorture 4.7.1
Using seed 1536072312
time: 2018-09-04 16:45:12.033129
test: list_shares
time: 2018-09-04 16:45:12.033632
Listing: smb://earth.milkyway.site
DIR: ADMIN$
DIR: C$
DIR: IPC$
DIR: NETLOGON
DIR: SYSVOL
time: 2018-09-04 16:45:12.041815
success: list_shares
So far my guess would be that the issue is in gvfs as I can successfully list shares with SMB3 only! However the issue could also be some very strange configuration of the SMB server.
Ondrej, I'm not able to reproduce this with KDE's kio_smb and Samba 4.8.4, forcing the protocol to SMB3!
I'm sorry, the referred Fedora issue is about "smb://workgroup", but this issue seems to be about "smb://server" and this should definitely work. I will make some tests tomorrow to see whether I can reproduce... Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:2145 |