I have several OSX machines in my network and every single one of them has issues losing connection to the ReadyNas while in use. Someone will be browsing the drive via SMB and then suddenly the connection will drop. While the users can easily reconnect, it is supremently annoying to be browsing and then have to reconnect.
OSX: 10.15.7
ReadyNAS firmware: 6.10.
Does anyone else have this problem?
I attempted to restrict the SMB version on ReadyNas to SMB 3.0.2 via the SMB Plus app. I noticed it will not connect if I restrict it to 3.1 or greater. Do I need to use an SMB version less than 3.0.2?
I attempted to restrict the SMB version on ReadyNas to SMB 3.0.2 via the SMB Plus app. I noticed it will not connect if I restrict it to 3.1 or greater. Do I need to use an SMB version less than 3.0.2?
I'm not a mac user, but I believe you can see the version of the SMB that your macs are actually using by entering smbutil statshares -a in terminal on the mac. (I suspect that will only work if the Mac is accessing a NAS share).
If SSH is enabled on the NAS, you can also see this info by entering smbstatus there (when the Mac is accessing a share).
Once you know the minimum SMB version used by your devices, you can restrict the server with SMB Plus.
I have several OSX machines in my network and every single one of them has issues losing connection to the ReadyNas while in use. Someone will be browsing the drive via SMB and then suddenly the connection will drop.
Again, I'm not a Mac user. I am seeing some reports of this happening with Catalina with various file servers (including Synology NAS btw).
One suggestion I saw on Reddit was to disable "allow disk to sleep" on the Mac. no idea why that would help - but it apparently did solve the problem for that person, and it would easy to try.
As for smb status: This is is what comes back for all the connections. Anything to be concerned about here?
Nothing to be concerned about, but it does confirm that OSX is using 3.0.2. That explains why removing that protocol verison with SMB Plus resulted in failed connections.
I haven't heard any complaints about the server from people who's machines who now have put drives to sleep option as off. It may have done the trick.
Good news, thank you for the update.
Unfortunatley, Apple does after decades not get a reliable proprietary SMB client implementation on thier proprietary OS to the field. Leaving SAMBA towards thier proprietary protocol implementation wasn't helping much (as expected) - except for adding even more non-transparent things to the user base. Almost every update does lead to new tiny issues and oddities - and this happened the second time in the year 2020 already now.
What makes sense on a NAS - permitting there are no legacy clients on a network (!!!) is to put the minimum version to v2 or v3.0 so no old protocol weaknesses can be abused by sniffing the traffic, or denying using unsigned or whatever feature.
What does not make much sense is to limit the highest v3 protocol version. Unless there are specific issues where an SMB client can't deal with the highest SMB version available on the server, leave it up to the NAS to offer the best possible protocol version. One day any SMB protocol or client OS maker does decide that say 3.02 isn't good enough, so you have to take admin actions again.
Leave the highest available to the SMB protocol version negotiation between the SMB client (Windows can, MacOS can, ...) and the NAS.
