Bug 1154823 - samba problems in TW snapshot 20191018
samba problems in TW snapshot 20191018
Status: RESOLVED FIXED
: 1156077 (view as bug list)
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Samba
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: The 'Opening Windows to a Wider World' guys
The 'Opening Windows to a Wider World' guys
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-10-23 08:43 UTC by Vadim Krevs
Modified: 2019-11-07 16:38 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vadim Krevs 2019-10-23 08:43:49 UTC
Just upgraded to TW snapshot 20191018 which resulted in 4.10.8+git.124.a2010fbd0de -> 4.11.0+git.95.c88b5f2c0c6 samba upgrade. 

I have a couple samba shares configured in Places in Dolphin and now clicking on them results in "Internal error. Please send a full bug report to https://bugs.kde.org. Unknown error condition in stat. Software caused connection abort".

There were no problems accessing these samba shares yesterday before the upgrade.

Another PC on the same LAN running openSUSE Leap 15.1 with samba-4.9.5+git.187.71edee57d5a-lp151.2.6.1.x86_64 has no problems accessing these samba shares.
Comment 1 Vadim Krevs 2019-10-23 16:21:58 UTC
Reverting to samba rpms from http://download.opensuse.org/history/20191016/tumbleweed/repo/oss/x86_64/ snapshot fixes the problem and samba shares are accessible again.
Comment 2 Samuel Cabrero 2019-10-23 16:23:54 UTC
Hi Vadim,

The biggest change in samba 4.11 is that SMB1 is disabled by default. This is the relevant part from the release notes:

> SMB1 is disabled by default
> ---------------------------
> 
> The defaults of 'client min protocol' and 'server min protocol'
> have been changed to SMB2_02.
> 
> This means clients without support for SMB2 or SMB3 are no longer
> able to connect to smbd (by default).
> 
> It also means client tools like smbclient and other,
> as well as applications making use of libsmbclient are no longer
> able to connect to servers without SMB2 or SMB3 support (by default).

From your description I guess tumbleweed is the client, so if this is the issue try adding 'client min protocol=NT1' to /etc/samba/smb.conf as a workaround while upgrading the server to use SMB 2.02 as minimum.

If this is not the issue, please provide logs to debug it.
Comment 3 Vadim Krevs 2019-10-23 17:07:39 UTC
Hi Samuel. 

Thank you for a prompt response. The suggested workaround - adding 'client min protocol=NT1' to /etc/samba/smb.conf - resolves the issue, much appreciated. 

Server upgrade is not an option unfortunately - it is an old media player, no firmware updates for a few years, etc.
Comment 4 Samuel Cabrero 2019-10-23 18:00:38 UTC
(In reply to Vadim Krevs from comment #3)
> Hi Samuel. 
> 
> Thank you for a prompt response. The suggested workaround - adding 'client
> min protocol=NT1' to /etc/samba/smb.conf - resolves the issue, much
> appreciated. 

You're welcome, glad to help.

> Server upgrade is not an option unfortunately - it is an old media player,
> no firmware updates for a few years, etc.

Please keep in mind SMB1 will be removed at some point. From release notes:

> SMB1 is officially deprecated and might be removed step by step
> in the following years. If you have a strong requirement for SMB1
> (except for supporting old Linux Kernels), please file a bug
> at https://bugzilla.samba.org and let us know about the details.
Comment 5 Rigo Wenning 2019-11-07 16:38:35 UTC
*** Bug 1156077 has been marked as a duplicate of this bug. ***