Very (very) new to linux/samba and ran into a smb protocol issue, I have primarily old win7 boxes, some win10 and now linux. Attempts to access shares in dolphin were only resolved with client min protocol in smb.conf.
It occurs to me that any smbv1 protocols on a workgroup are either an error, or an approved design requirement. I propose that when Dolphin attempts a usr/pwd using the smbv3 that results in a failure, it should then retry with smbv2, and a smbv2 failure should retry as smbv1. Which protocols and what order the rollback action would use would be defined in a conf file. The conf file would also provide options to log/msg auth situations that work and/or fail and if a rollback attempt was involved
The concept of rolling back to a previous protocol might also apply to other supported network services I don’t use. I believe rollbacks for dolphin initiated share mounts combined with logging offers:
- Seamless user experience with cleaner UI and fewer unexpected prompts
- Reduces help-desk calls for legacy device connectivity issues
- Security-conscious admins control which protocols and in what order they are allowed on a per box basis
- Allows separate client/server admin policies for smb delivery and access
- Offers an audit trail for troubleshooting
- Helps identify systems requiring correction or migration away from older protocols