NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OSX machines constantly disconnect from ReadyNAS
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 con...
Thanks for the info.
I am running 6.10.3. Typo on my original email!
I'll turn off the allow disk sleep on a couple of the macs and leave it unchanged on the others. I'll monitor the increase/decrease of complaints. =)
As for smb status: This is is what comes back for all the connections. Anything to be concerned about here?
SMB_NEGOTIATE SMBV_NEG_SMB1_ENABLED
SMB_NEGOTIATE SMBV_NEG_SMB2_ENABLED
SMB_NEGOTIATE SMBV_NEG_SMB3_ENABLED
SMB_VERSION SMB_3.02
SMB_SHARE_TYPE DISK
SIGNING_SUPPORTED TRUE
EXTENDED_SECURITY_SUPPORTED TRUE
UNIX_SUPPORT TRUE
LARGE_FILE_SUPPORTED TRUE
OS_X_SERVER TRUE
DFS_SUPPORTED TRUE
FILE_LEASING_SUPPORTED TRUE
MULTI_CREDIT_SUPPORTED TRUE
dtarin wrote:
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.
I'll continue monitoring but that little change seems promising.
dtarin wrote: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.
dtarin wrote:I'll continue monitoring but that little change seems promising.
Let me come back to the idea of manually tweaking the ReadyNAS (or any other SAMBA based NAS) protocol requirements.
Leaving AFP alone, MacOS does only offer cifs and smb. Using
smb://server/public
does lead to
smbutil statshares -m /Volumes/public/
...SMB_NEGOTIATE SMBV_NEG_SMB1_ENABLED
SMB_NEGOTIATE SMBV_NEG_SMB2_ENABLED
SMB_NEGOTIATE SMBV_NEG_SMB3_ENABLED
SMB_VERSION SMB_3.02So this is the highest common protocol version negotiated between Apple's SMB client and the NAS. Using
cifs://server/public
does lead to
smbutil statshares -m /Volumes/public/
...
SMB_NEGOTIATE SMBV_NEG_SMB1_ONLY
SMB_VERSION SMB_1So SMB 1.0, the legacy "CIFS" version.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
