RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1619719 - Cannot browse SMB shares from GNOME after update to RHEL 7.5
Summary: Cannot browse SMB shares from GNOME after update to RHEL 7.5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gvfs
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ondrej Holy
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1650452 1658690
Blocks: 1656436 1739116
TreeView+ depends on / blocked
 
Reported: 2018-08-21 14:56 UTC by Skip Wyatt
Modified: 2023-03-24 14:11 UTC (History)
12 users (show)

Fixed In Version: gvfs-1.36.2-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1739116 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:57:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2145 0 None None None 2019-08-06 12:58:03 UTC

Description Skip Wyatt 2018-08-21 14:56:12 UTC 
Description of problem:
After upgrade to RHEL 7.5, customer cannot browse smb shares.
This works in RHEL 7.4

Version-Release number of selected component (if applicable):

samba-4.7.1-9.el7_5.x86_64
samba-client-4.7.1-9.el7_5.x86_64
samba-client-libs-4.7.1-9.el7_5.x86_64
samba-common-4.7.1-9.el7_5.noarch
samba-common-libs-4.7.1-9.el7_5.x86_64
samba-common-tools-4.7.1-9.el7_5.x86_64
samba-libs-4.7.1-9.el7_5.x86_64
samba-winbind-4.7.1-9.el7_5.x86_64
samba-winbind-krb5-locator-4.7.1-9.el7_5.x86_64
samba-winbind-modules-4.7.1-9.el7_5.x86_64
nautilus-3.22.3-5.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Upgrade system to RHEL 7.5
2. Attempt to Browse SMB shares
3.

Actual results:
Browse does not work

Expected results:
Customer should see Windows Shares on Network

Additional info:
Comment 3 Andreas Schneider 2018-08-23 14:56:41 UTC 
Can you please be more precise what this means?

Do you mean that connecting to smb://server doesn't list the available shares?
Comment 5 Andreas Schneider 2018-08-27 15:19:30 UTC 
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().
Comment 6 Andreas Schneider 2018-08-27 17:10:10 UTC 
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.
Comment 7 Ondrej Holy 2018-08-28 06:11:35 UTC 
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...
Comment 8 Skip Wyatt 2018-08-28 12:55:40 UTC 
Andreas,

When connecting using GNOME files connecting to smb://<servername> returns no shares.

-Skip
Comment 9 Andreas Schneider 2018-09-04 15:00:09 UTC 
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!
Comment 10 Ondrej Holy 2018-09-05 14:48:41 UTC 
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...
Comment 25 errata-xmlrpc 2019-08-06 12:57:59 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.