To resolve this performance issue you can force OS X to disable client signing over SMB by using the /etc/nf file that contains the following.Īfter a reboot, your SMB mount will no longer require client signing and performance should be restored. Microsoft documentation regarding “client signing” states that enabling this can degrade performance by as much as 15% percent, however this performance impact seems to grow exponentially with the available bandwidth.Īs you can see from the chart below, there is a performance hit with enabling client signing, and depending on your connection speed and SMB protocol used (SMB2/SMB3) the performance hit can be substantial. This was most likely done as an added security measure due to a security bug in the SMB protocol identified by Microsoft and Samba. With 10.11.5 and higher, Apple is now forcing “client signing” by default for SMB connections.
AFP SHEEPSHAVER MACOS SIERRA MAC
With multiple versions of the Mac operating systems being littered with SMB compatibility issues: ranging from performance penalties, authentication issues, and the inability to mount volumes using SMB2/SMB3, forcing some users to mount with the slower CIFS protocol, further affecting performance.Ī lot of the SMB issues appeared to have been resolved with El Capitan, but if you’ve updated to OS X 10.11.5 and higher your SMB performance may once again be impacted. This transition has been a bit rocky for some Apple users.
Slowly transitioning services from AFP to Samba, then moving from Samba to SMB2/SMB3 to maintain compatibility with Microsoft. Since OS X 10.8.x Apple has progressively been moving away from AFP to a more agnostic network protocol.