Hai,
Please read : https://www.samba.org/samba/history/samba-4.11.0.html
Which states:
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).
It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2
and LANMAN1 for client and server, as well as CORE and COREPLUS on
the client.
Note that most commandline tools e.g. smbclient, smbcacls and others
also support the '--option' argument to overwrite smb.conf options,
e.g. --option='client min protocol=NT1' might be useful.
As Microsoft no longer installs SMB1 support in recent releases
or uninstalls it after 30 days without usage, the Samba Team
tries to get remove the SMB1 usage as much as possible.
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.
Regards,
Louis
> -Oorspronkelijk bericht-
> Van: Pkg-samba-maint
> [mailto:pkg-samba-maint-bounces+belle=bazuin.nl@alioth-lists.d
> ebian.net] Namens Igor Liferenko
> Verzonden: woensdag 16 oktober 2019 11:17
> Aan: Debian Bug Tracking System
> Onderwerp: [Pkg-samba-maint] Bug#942433: samba: Cannot mount
> share on samba3 server from samba4 client: protocol negotiation failed
>
> Package: samba
> Version: 2:4.11.0+dfsg-10
> Severity: important
>
> Dear Maintainer,
>
> After upgrade from samba 4.9.13 to 4.11.0, mounting shares
> from samba3 server stopped working.
>
> Here is the output of "GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd
> --replace" from
> "gio mount smb://x.x.x.x/doc/":
>
> smb: g_vfs_backend_smb_init: default workgroup = 'NULL'
> smb: Added new job source 0x55c74aa13080 (GVfsBackendSmb)
> smb: Queued new job 0x55c74aa15140 (GVfsJobMount)
> smb: do_mount - URI = smb://x.x.x.x/doc
> smb: do_mount - try #0
> smb: auth_callback - kerberos pass
> smb: auth_callback - out: last_user = 'user', last_domain = 'XGROUP'
> smb: do_mount - [smb://x.x.x.x/doc; 0] res = -1, cancelled =
> 0, errno = [103] 'Software caused connection abort'
> smb: do_mount - (errno != EPERM && errno != EACCES),
> cancelled = 0, breaking
> smb: send_reply(0x55c74aa15140), failed=1 (Failed to mount
> Windows share: Software caused connection abort)
>
>
>
> Wireshark shows only one packet from client after connecting
> to server:
>"Protocol" header in wireshark is "SMB2" and "Info" header
> is "Negotiate Protocol Request"
> and then server closes connection.
>
>
>
> Here is config of samba3 server:
>
> [global]
> dos charset = 866
> unix charset = UTF8
> workgroup = USVGROUP
> server string = %h server
> interfaces = 127.0.0.0/8, x.x.x.x/24
> security = SHARE
> obey pam restrictions = Yes
> pam password change = Yes
> passwd program = /usr/bin/passwd %u
> passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
> unix password sync = Yes
> syslog = 0
> log file = /var/log/samba/log.%m
> max log size = 1000
> dns proxy = No
> panic action = /usr/share/samba/panic-action %d
> veto files = /lost+found/
> [doc]
> path = /home/doc/
> read only = No
> guest ok = Yes
>
>
>
>
> *** Reporter, please consider answering these questions,
> where appropriate ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
> -- Package-specific info:
> * /etc/samba/smb.conf present, and attached
> * /var/lib/samba/dhcp.conf not present
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
> (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor:
