El Capitan 10.11.5 update SMB slow (bug)

Has someone tested with beta 10.11.6?

one more here using WD Cloud

I was able to turn on ftp and using cyberduck to upload as a workaround for now. Speeds are pretty good

ChisolmLee15 wrote:

I should have also added:

Make sure that your Group name ("GROUPNAS") is in

System Preferences > Network > Advanced > WINS > Workgroup: GROUPNAS

And I found a tip re SMB 3 on the Synology NAS device.

Unable to connect to NAS Shared Folder in Finder (post by "VikingOSX")

-

I have always set the Group name for all of my devices, including my MBP and MyCloud. Makes no difference.

I'm also experiencing slow speeds with SMB since having updated to 10.11.5.

Before the update, I was getting proper speeds of 500 to 800 MB/s read and write via SMB3 to my server, which is a FreeNAS derivative. Since updating to 10.11.5, I'm not getting and speeds above 65 MB/s read or write. Nothing else has changed.

My server's running Samba 4.3.6.

I can also confirm that testing a dataset with an AFP share produces good speeds, at over 700 MB/s, for both read and write.

I can also confirm that setting the server to SMB2 only doesn't resolve the issue either. SMB2 is reading and writing at about 40 MB/s, and SMB3 is reading and writing at about 60 MB/s.

Recent testparm command output [scrubbed all personal info] from a Mac OS 10.6.8 "Snow Leopard" machine; I'm wondering (if you have the time) what the testparm output looks like from Samba on your FreeNAS? Tx.

$ testparm

Load smb config files from /private/etc/smb.conf

Processing section "[homes]"

Processing section "[SHRTHIS]"

Processing section "[printers]"

Loaded services file OK.

Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

[global]

dos charset = CP437

display charset = UTF-8

workgroup = HQ

realm = LKDC:SHA1.24651152E8CD333C5515E276A1056B6B2C888E9B

server string = Somebodys-Mac

auth methods = odsam

obey pam restrictions = Yes

passdb backend = odsam

lanman auth = No

use kerberos keytab = Yes

log level = 1

debug pid = Yes

max xmit = 131072

name resolve order = lmhosts wins bcast host

max smbd processes = 10

printcap name = cups

stat cache = No

os level = 2

preferred master = No

domain master = No

idmap domains = default

idmap alloc backend = odsam

idmap negative cache time = 5

com.apple:show admin all volumes = yes

com.apple:lkdc realm = LKDC:SHA1.24651152E8CD333C5515E276A1056B6B2C888E9B

com.apple:filter shares by access = yes

darwin_streams:brlm = yes

idmap config default:backend = odsam

idmap config default:default = yes

ea support = Yes

stream support = Yes

use sendfile = Yes

mangled names = No

include = /var/db/samba/smb.shares

wide links = No

vfs objects = notify_kqueue, darwinacl, darwin_streams

[homes]

comment = User Home Directories

valid users = %S

read only = No

create mask = 0750

browseable = No

include = /var/db/smb.conf

[SHRTHIS]

comment = SHRTHIS

path = /Volumes/SHRTHIS

read only = No

create mask = 0644

guest ok = Yes

[printers]

comment = All Printers

path = /tmp

create mask = 0700

printable = Yes

browseable = No

I went ahead and changed the maximum protocol back to SMB3_00, and didn't set a minimum protocol. Here, with some redacted personal info, are the outputs for testparm on the FreeNAS.

Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE


Press enter to see a dump of your service definitions


# Global parameters
[global]
  dos charset = CP437
  server string = Jupiter Server
  interfaces = [REDACTED]
  bind interfaces only = Yes
  server role = standalone server
  security = USER
  map to guest 
  obey pam restrictions = Yes
  logging = file
  max log size = 51200
  server max protocol = SMB3_00
  max protocol = SMB3_00
  protocol = SMB3_00
  time server = Yes
  deadtime = 15
  kernel change notify = No
  max open files = 7547978
  load printers = No
  printcap name = /dev/null
  disable spoolss = Yes
  lm announce = Yes
  dns proxy = No
  pid directory = /var/run/samba
  panic action = /usr/local/libexec/samba/samba-backtrace
  nsupdate command = /usr/local/bin/samba-nsupdate -g
  idmap config *: range = 90000001-100000000
  idmap config * : backend = tdb
  acl allow execute always = Yes
  create mask = 0666
  directory mask = 0777
  directory mode = 0777
  ea support = Yes
  directory name cache size = 0
  store dos attributes = Yes
  strict locking = No
  dos filemode = Yes





[TYPICAL SHARE]
  path = [REDACTED]
  read only = No
  veto files = /.snapshot/.windows/.mac/.zfs/
  vfs objects = zfs_space zfsacl aio_pthread streams_xattr netatalk recycle
  zfsacl:acesort = dontcare
  nfs4:chown = true
  nfs4:acedup = merge
  nfs4:mode = special
  recycle:subdir_mode = 0700
  recycle:directory_mode = 0777
  recycle:touch = yes
  recycle:versions = yes
  recycle:keeptree = yes
  recycle:repository = .recycle/%U

Re SMB 3 - SMB signing required

The purpose of that post, was to nudge readers to also read the next few after it; especially here:

ebaauwMay 24, 2016 9:09 PM Re: iOS File Share apps unable to access File Shares since 10.11.5
in response to ebaauwSolved

I can confirm that the issue is indeed that SMB signing is now forced on the Mac server by default. The good news: this can be disabled manually by editing /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist and add a new key:

<key>SigningRequired</key>

<false/>

After restarting the smbd process, the apps on my iPad can connect again, as before the 10.11.5 / server 5.1.5 upgrade.

You might find the file on your Mac (even though your Mac is not a Mac OS 10.11.5 / 5.1.5 server):

/Library/Preferences/SystemConfiguration/com.apple.smb.server.plist

and test.

-

ChisolmLee15 wrote:

Re SMB 3 - SMB signing required

The purpose of that post, was to nudge readers to also read the next few after it; especially here:

ebaauwMay 24, 2016 9:09 PM Re: iOS File Share apps unable to access File Shares since 10.11.5
in response to ebaauwSolved

I can confirm that the issue is indeed that SMB signing is now forced on the Mac server by default. The good news: this can be disabled manually by editing /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist and add a new key:

<key>SigningRequired</key>

<false/>

After restarting the smbd process, the apps on my iPad can connect again, as before the 10.11.5 / server 5.1.5 upgrade.

You might find the file on your Mac (even though your Mac is not a Mac OS 10.11.5 / 5.1.5 server):

/Library/Preferences/SystemConfiguration/com.apple.smb.server.plist

and test.

-

I talked to an Apple enterprise-level phone tech, and they said that while they were aware of that suggestion to modify the dictionary, they couldn't recommend it as an optimal, effective, or permanent fix.

I appreciate all your replies and test results. I'm only investigating and not expecting a permanent fix at this time. Also, trying to provide info and tools for others to consider.

MacWindows.com has a collection of detailed info (year 2014) on users' discoveries and efforts to find answers - re Mac OS 10.9.n "Mavericks" file sharing problems.

MacWindows.com's Yosemite snapshot re same issue of SMB / SMB 2 / SMB 3.

-

Same problem here. I'm able to connect to my Synology SMB shares but I get about 25-100 Mbps instead of 700-900 Mbps. Fix it ASAP!

uryupinsk wrote:

Same problem here. I'm able to connect to my Synology SMB shares but I get about 25-100 Mbps instead of 700-900 Mbps. Fix it ASAP!

This is a user to user forum. If you want Apple to do something, you should tell them. The more people that actually contact Apple about this the better.

BugReporter

Anyone can get a free account at:

<https://developer.apple.com/register/index.action>

I am having the same problem with 10.11.5, mine is with a WD MyBookLive NAS that fails using SMB but runs really slowly using CIFS. And the addition of <key>SigningRequired</key> <false/> to com.apple.smb.server.plist did not fix the problem, in my case. Following.