Should be configurable in web UI then. With a big warning sign. ![]()
Thanks for the suggestion.
Ordinary users probably not understand the difference of server protocol between v1-v3, so this configuration may not be displayed in the GL GUI (since will increase some misunderstandings or misuse). Anyway will default to v2 if users' voices enough.
Im fine with using V2, most if not all computers now days won't have an issue with it. Its like most people still use Windows XP.
SMB1 is from 1990...
SMB2 is from 2010...
SMB3 is from 2013...
I guess we should not see any problem even when using SMB3 ![]()
Samba 4 was released in 2019 and its almost 2025.
I'm using SMB3 protocol because I don't have any device prior to Windows 10.
From what I found, SMB3 refers to SMB3_11 variant on smb.conf:
Update and clarify, after we detailed check, /etc/samba/smb.conf, server min protocol = CORE
Although the configuration file is written CORE, actually, samba will automatically conduct agreement negotiation:
If the samba client supports SMB3, the server willl be upgraded to SMB3 even if the CORE is configured.
BWT, this is for better compatibility and performance.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.


