Samplex

Q: El Capitan 10.11.5 update SMB slow (bug)

Since i upgraded my Macbook Pro Retina 2015 to 10.11.5 SMB transfers speeds to my Synology NAS are not going faster then 25Mbit.

When i use AFP i get 110Mbit speeds to my nas.

 

Tested a Mac Mini which has 10.11.4 and the SMB and AFP speeds are good 110Mbit.

Upgraded that mac mini to 10.11.5 and i get 25Mbit speed max using SMB!

 

Seems like bug in the SMB protocol of El Capitan release 10.11.5

MacBook Pro with Retina display, OS X El Capitan (10.11.5)

Posted on May 18, 2016 7:45 AM

Close

Q: El Capitan 10.11.5 update SMB slow (bug)

  • All replies
  • Helpful answers

first Previous Page 5 of 9 last Next
  • by BobHarris,

    BobHarris BobHarris May 27, 2016 7:44 AM in response to kmurphy1
    Level 6 (19,257 points)
    Mac OS X
    May 27, 2016 7:44 AM in response to kmurphy1

    kmurphy1 wrote:

     

    sjb100 wrote:

     

    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.

    aaron-OZ wrote:

     

    While Apple is working on a patch for this I've seen this reported fix on Twitter...

    https://twitter.com/mikeymikey/status/735887722313719808

    These suggestions both accomplish the same thing.

    Unfortunately neither method is working for me. Although I'm trying to connect to a Windows 7 shared folder, not a NAS. But it's the same SMB issue. CIFS works (slowly) for now.


    I reported this bug to Apple, and this was their response: Screen Shot 2016-05-27 at 10.15.55 AM.png

    I can't seem to get either of those echo commands to run. Terminal responds with "-bash: /etc/nsmb.conf: Permission denied" every time. I also tried those commands with sudo and it still says permission denied.

    sudo echo "[default]"                    >/etc/nsmb.conf

    sudo echo signing_required=no >>/etc/nsmb.conf

  • by kmurphy1,

    kmurphy1 kmurphy1 May 27, 2016 8:48 AM in response to BobHarris
    Level 1 (14 points)
    Mac OS X
    May 27, 2016 8:48 AM in response to BobHarris

    As I said before, sudo doesn't work either.

    Screen Shot 2016-05-27 at 11.46.04 AM.png

    That file ( /etc/nsmb.conf ) doesn't even exist on my machine.

    Screen Shot 2016-05-27 at 11.47.37 AM.png

  • by Seth Goldin,

    Seth Goldin Seth Goldin May 27, 2016 8:54 AM in response to BobHarris
    Level 1 (4 points)
    Mac OS X
    May 27, 2016 8:54 AM in response to BobHarris

    Via my contact in the Apple enterprise department, the engineers requested more data from me this morning. The good engineers at Apple seem to be actively working on this. My problem is occurring with a FreeBSD NAS, so they requested client-side data from the 10.11.5 machine. I sent them what they requested:

     

    1. I enabled client side debugging from Terminal
    2. I increased the SMB logging level for debugging
    3. I initiated a packet trace with tcpdump over the interface being used for the SMB share
    4. With tcpdump "listening," I sent some traffic back and forth with Blackmagic Disk Speed Test.
    5. I sent the resulting PCAP file to the Apple.

     

    Stay tuned!

  • by BobHarris,Helpful

    BobHarris BobHarris May 27, 2016 12:30 PM in response to kmurphy1
    Level 6 (19,257 points)
    Mac OS X
    May 27, 2016 12:30 PM in response to kmurphy1

    As I said before, sudo doesn't work either.

     

    OK.  I understand now.  This will be just a little more complex

    sudo -s

    Password: <your account's password here>

    echo "[default]"                    >/etc/nsmb.conf

    echo signing_required=no >>/etc/nsmb.conf

    exit

  • by kmurphy1,

    kmurphy1 kmurphy1 May 27, 2016 1:04 PM in response to BobHarris
    Level 1 (14 points)
    Mac OS X
    May 27, 2016 1:04 PM in response to BobHarris

    BobHarris wrote:

     

    OK.  I understand now.  This will be just a little more complex

    sudo -s

    Password: <your account's password here>

    echo "[default]"                    >/etc/nsmb.conf

    echo signing_required=no >>/etc/nsmb.conf

    exit

    That worked! Thank you so much, Bob!

    That fixed SMB shared folders, AND shared printers!

     

    You're my hero.

     

    Edit:

    Just to clarify for anyone reading this post, I entered the above commands in the Terminal, and then restarted my computer.

    I'm not positive, but I don't think it will work without restarting (or at least logging out and back in) afterwards.

  • by Ibanezq,

    Ibanezq Ibanezq May 27, 2016 10:51 PM in response to kmurphy1
    Level 1 (4 points)
    Mac OS X
    May 27, 2016 10:51 PM in response to kmurphy1

    Someone else can confirm that this method solve the SMB problem?

  • by elchdergrosse,

    elchdergrosse elchdergrosse May 28, 2016 7:26 AM in response to Ibanezq
    Level 1 (4 points)
    Mac OS X
    May 28, 2016 7:26 AM in response to Ibanezq

    Yes - worked for me. Back with about 100Mb/s from/to my NAS

  • by Krutsch,

    Krutsch Krutsch May 28, 2016 7:46 AM in response to Ibanezq
    Level 1 (9 points)
    May 28, 2016 7:46 AM in response to Ibanezq

    Ibanezq wrote:

     

    Someone else can confirm that this method solve the SMB problem?

     

    Mostly, I would say 'Yes'. I am able to connect with smb://... as before and the performance is close to what I was seeing before.

  • by WalkyChalky,

    WalkyChalky WalkyChalky May 28, 2016 11:30 AM in response to kmurphy1
    Level 1 (4 points)
    May 28, 2016 11:30 AM in response to kmurphy1

    Can someone clarify how to properly enter these commands in Terminal.?I am a Terminal novice and the commands beyond entering my password don't seem to be working. After each command I enter I just get a new line starting with "[bash-3.2#". Is this right? Please help.

  • by Ibanezq,

    Ibanezq Ibanezq May 28, 2016 11:34 AM in response to WalkyChalky
    Level 1 (4 points)
    Mac OS X
    May 28, 2016 11:34 AM in response to WalkyChalky
  • by WalkyChalky,

    WalkyChalky WalkyChalky May 28, 2016 11:53 AM in response to Ibanezq
    Level 1 (4 points)
    May 28, 2016 11:53 AM in response to Ibanezq

    I unlocked the SIP now, but still same issue. I am just copying and pasting each of the following lines into terminal and pressing enter after each:

     

    sudo -s

    Password: <your account's password here>

    echo "[default]"                    >/etc/nsmb.conf

    echo signing_required=no >>/etc/nsmb.conf

    exit

     

    The two that begin with echo don't seem to do anything.

     

    Am i doing something wrong?

  • by AgentMax81,

    AgentMax81 AgentMax81 May 28, 2016 12:00 PM in response to WalkyChalky
    Level 1 (8 points)
    iTunes
    May 28, 2016 12:00 PM in response to WalkyChalky

    You don't need to unlock SIP.

    ANd you don't get visible feedback after entering the commands and hitting return.

  • by WalkyChalky,

    WalkyChalky WalkyChalky May 28, 2016 12:11 PM in response to AgentMax81
    Level 1 (4 points)
    May 28, 2016 12:11 PM in response to AgentMax81

    Thanks Max! It's working now. Tried both this method and editing the keys for the smb plist file per this thread : https://discussions.apple.com/message/30246066#30246066

     

    Not sure which one did the trick but I'm not gonna complain. My Sonos share looks like its back up!!

     

    This was way too much of a headache though. Remember when things "just worked"? I miss Steve Jobs...

  • by sjb100,

    sjb100 sjb100 May 28, 2016 12:31 PM in response to Krutsch
    Level 1 (4 points)
    Mac OS X
    May 28, 2016 12:31 PM in response to Krutsch

    It worked in one respect for me, but not totally. Although I was able to access the WD MyBook Live NAS after creating /etc/nsmb.conf and switching back from CIFS to SMB, it was really, really slow (even slower than CIFS) when it came to Finder and iTunes library access. It was so bad I ended up switching back to CIFS, removing the /etc/nsmb.conf file.

  • by Bill Scott,

    Bill Scott Bill Scott May 28, 2016 9:30 PM in response to BobHarris
    Level 6 (11,449 points)
    May 28, 2016 9:30 PM in response to BobHarris

    Is it possible this is also the cause of very slow drag-and-drop copying via Apple Screen-sharing ?  (I assumed it was AFP-based, but now I am reading it might be SMB.)

first Previous Page 5 of 9 last Next