Bug#883939: smbclient failing to connect with default protocol SMB3_11
As an update, I still have this behavior on my stretch machine running smbclient version 4.5.16+dfsg-1+deb9u2. However, on an installation of buster running smbclient version 4.9.5+dfsg-5, I do not have the bug. The two installations are not identical however. The stretch machine is a server and the buster machine just has smbclient installed. It may be that "my" bug is different than the originally reported problem in any case. David
Bug#883939: smbclient failing to connect with default protocol SMB3_11
Only thing i can suggest atm for this one is post your problem on the samba list. If you do, post the windows server version your using also. And preffered also the linux os and smb.conf ( if needed anonymized ). This might be a regression or a "still" not fixed bug. Best regards, Louis > -Oorspronkelijk bericht- > Van: Matthew Foulkes [mailto:m.foul...@blueyonder.co.uk] > Verzonden: vrijdag 24 augustus 2018 13:56 > Aan: 883...@bugs.debian.org; L.P.H. van Belle > Onderwerp: Re: smbclient failing to connect with default > protocol SMB3_11 > > Hi Louis, > > Thanks for your help, but this bug does not seem to be quite > the same as > any of the ones you listed. I can connect when I specify "client max > protocol" values of SMB3_10, SMB3_02, SMB2, or NT1, but not > with SMB3 or > SMB3_11. > > Best wishes, Matthew > > -- > ** > email: m.foul...@blueyonder.co.uk > phone: (020) 8286 9910 > ** > >
Bug#883939: smbclient failing to connect with default protocol SMB3_11
Hi Louis, Thanks for your help, but this bug does not seem to be quite the same as any of the ones you listed. I can connect when I specify "client max protocol" values of SMB3_10, SMB3_02, SMB2, or NT1, but not with SMB3 or SMB3_11. Best wishes, Matthew -- ** email: m.foul...@blueyonder.co.uk phone: (020) 8286 9910 **
Bug#883939: smbclient failing to connect with default protocol SMB3_11
Hai, The cause of these "bugs" are security updates and windows removeing/disabling smb1. Samba/Windows are disabling SMB1 and changing the defaults for smbclient from smb1 to smb3. Take also note of this: Every windows 10 1709 and up please note that.. If you dont use your windows 10 for 2 weeks, SMB1 is automaticly removed. After you reinstall it, it wont be removed anymore. Some related bugs: This is your problem. https://bugzilla.samba.org/show_bug.cgi?id=12895 i believe this one is also related to this problem. https://bugzilla.samba.org/show_bug.cgi?id=12876 one to watch out. https://bugzilla.samba.org/show_bug.cgi?id=13360 Do not allow ntlmv1 over SMB1 when it is disabled via "ntlm auth". ( fixed, but reopened ) https://bugzilla.samba.org/show_bug.cgi?id=13328 samba 4.7 is where the default setting changed. client max protocol Effective SMB3_11 default changed Based on what i've seen on the samba (bug) list, i dont think this is fully fixed. I hope this info helps out a bit. Best regards, Louis
Bug#883939: smbclient failing to connect with default protocol SMB3_11
I am also seeing this same bug in Debian v9.3 stretch. I have smbclient version 4.5.12+dfsg-2+deb9u1. The fix suggested of setting client "max protocol = SMB3_10" in /etc/samba/smb.conf also fixed the problem for me. I’ll say that I’m specifically connecting to a Windows 10 client with all the latest security updates. Not sure when this problem started but I believe since I upgraded to stretch late last year. I can provide any other info requested. Thanks
Bug#883939: smbclient failing to connect with default protocol SMB3_11
Package: smbclient Version: 2:4.7.3+dfsg-1 Severity: important Dear Maintainer, Today, for the first time for years, I tried to use smbclient to access files on a Windows file server at work. After discovering that the Thunar file manager was unable to connect, I tried smbclient. The command smbclient -d 10 -W IC -U wmcfoulkes //icnas2.cc.ic.ac.uk/wmcfoulkes failed with the error message protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE as did: smbclient -m SMB3 -d 10 -W IC -U wmcfoulkes //icnas2.cc.ic.ac.uk/wmcfoulkes smbclient -m SMB3_11 -d 10 -W IC -U wmcfoulkes //icnas2.cc.ic.ac.uk/wmcfoulkes Specifying "-m SMB3_10" or any lower protocol version on the command line solved the problem. Setting "client max protocol = SMB3_10" in /etc/samba/smb.conf fixed Thunar too. It is possible that the Windows server (to which I do not have access) does not support SMB3_11, but I would have expected automatic negotiation to a lower protocol version to work. I have attached the logs obtained when smbclient is run with "-d 10 -m SMB3_11" and "-d 10 -m SMB3_10". Best wishes, Matthew -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smbclient depends on: ii dpkg 1.19.0.4 ii libarchive13 3.2.2-3.1 ii libbsd0 0.8.6-3 ii libc6 2.25-3 ii libpopt0 1.16-10+b2 ii libreadline7 7.0-3 ii libsmbclient 2:4.7.3+dfsg-1 ii libtalloc22.1.10-2 ii libtevent00.9.34-1 ii samba-common 2:4.7.3+dfsg-1 ii samba-libs2:4.7.3+dfsg-1 smbclient recommends no packages. Versions of packages smbclient suggests: pn cifs-utils pn heimdal-clients -- no debconf information INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 Processing section "[global]" doing parameter workgroup = WORKGROUP doing parameter dns proxy = no doing parameter log file = /var/log/samba/log.%m doing parameter max log size = 1000 doing parameter syslog = 0 WARNING: The "syslog" option is deprecated doing parameter panic action = /usr/share/samba/panic-action %d doing parameter server role = standalone server doing parameter passdb backend = tdbsam doing parameter obey pam restrictions = yes doing parameter unix password sync = yes doing parameter passwd program = /usr/bin/passwd %u doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . doing parameter pam password change = yes doing parameter map to guest = bad user doing parameter usershare allow guests = yes pm_process() returned Yes lp_servicenumber: couldn't find homes added interface enp0s25 ip=192.168.1.34 bcast=192.168.1.255 netmask=255.255.255.0 Netbios name list:- my_netbios_names[0]="BEE" Client started (version 4.7.3-Debian). Opening cache file at /var/cache/samba/gencache.tdb tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: No such file or directory Attempt to open gencache.tdb has failed. sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up icnas2.cc.ic.ac.uk#20 (sitename (null)) Opening cache file at /var/cache/samba/gencache.tdb tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: No such file or directory Attempt to open gencache.tdb has failed. no entry for icnas2.cc.ic.ac.uk#20 found. resolve_hosts: Attempting host lookup for name icnas2.cc.ic.ac.uk<0x20> remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 2 addresses for icnas2.cc.ic.ac.uk#20:
