Julian Alarcon, this report is scoped only to not getting maximum
negotiation upon a successful connection, not your problem of it won't
connect at all.
However, given the security implications of using NT1, the original
premise of this report isn't valid, and is no longer of use to me as the
Ok, I check and the Windows 10 client have disabled the SMBv1 protocol.
But the next version of Windows Server will disable it by default:
https://support.microsoft.com/en-au/help/4034314/smbv1-is-not-installed-by-default-in-windows-10-rs3-and-windows-server
*---*
- Windows 10 Enterprise and
It shouldn't be marked as invalid. I can't access Shared FOlders of
Windows 10 using Ubuntu 17.10 on Nautilus, I found a workaround, use
option -m SMB3 (I have to change smb.conf).
julian@e01a27166:/var/log/samba$ smbclient -L //10.80.35.54 -U julian.alarcon
-m SMB1
WARNING: Ignoring invalid
It shouldn't be marked as invalid. I can't access Shared Folders of
Windows 10 using Ubuntu 17.10 on Nautilus, I found a workaround, use
option -m SMB3 (I have to change smb.conf).
julian@e01a27166:/var/log/samba$ smbclient -L //10.80.35.54 -U julian.alarcon
-m SMB1
WARNING: Ignoring invalid
Upstream is slowly changing its default regarding the protocol. Just
today I saw a patch in the ML changing the CIFS default from SMB1 to
SMB3, and a few weeks ago a bunch of test changes were landing also as a
result of changing protocol versions. We are getting there.
--
You received this bug
Upstream is slowly changing its default regarding the protocol. Just
today I saw a patch in the ML changing the CIFS default from SMB1 to
SMB3, and a few weeks ago a bunch of test changes were landing also as a
result of changing protocol versions. We are getting there.
--
You received this bug
I'm using Zesty, which speaks at 3.1.1 dialect with Windows 10.
** Changed in: samba (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598463
Title:
samba
client max protocol = SMB3_11 may help, but that's not the default as not
everything is completely
working (on the client side) in this mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598463
