Home » Mac, Reviews, how to

OS X Mavericks SMB2 Troubles? Here’s a Workaround

28 October 2013 8,528 views 2 Comments

Of the relatively few OS X 10.9 issues that pop up repeatedly, the Mavericks SMB2 connection problem is perhaps the most vexing…

Apple’s OS X Mavericks rollout, though not perfect, has been pretty darned smooth. Of the relatively few issues that pop up repeatedly, the Mavericks SMB2 connection problem is perhaps the most vexing. Although there isn’t fix yet, there are workarounds.

The issue likely stems from the fact that Apple has made major changes to how computers connect to each other in OS X 10.9. Specifically, with Mavericks, Apple is transitioning away from the AFP (Apple Filing Protocol) and SMB1 protocols in favor of the SMB2 standard used in Windows and Linux.

Yes, AFP and SMB1 are both still in Apple’s network stack, for compatibility with older machines, but SMB2 is now the default.

Whereas I’ve been hearing about Mavericks SMB2 + Linux connection issues from friends, others are reporting that problem is more general:

“In my case, I got the double foul. My NAS tried to mount forever and failed; same with a Windows 8 PC on my network,” writes Mel Martin, TUAW. “The cause appears to be changes made in the networking stack made by Apple. Apple’s SMB2 implementation doesn’t work with a lot of SMB2 devices — even networked drives from Windows machines.”

Mavericks SMB2: Working It Out

Again, although there isn’t a fix yet available for these problems, Michael Larsen has written up the issue, as well as a work around:

Issue: Clients logging into File Services over SMB with OS X 10.9 experience hanging connection upon login attempt.

Root Cause: OS X 10.9 now utilizes a new SMB2 stack written by Apple. Apple’s SMB2 implementation is not compatible with many other SMB2 NAS products on the market today while Windows 7, 8, and 8.1 works just fine. In short, its an Apple bug.

Workaround: To force your connection to be SMB1, simply type cifs://servername instead of smb://servername when connecting to a Windows or NAS share.

Larsen notes that a quick restart before trying this Mavericks SMB2 connectivity workaround could be helpful in that it will purge any hung processes that could bugger things up.

Larsen also spells out a more permanent workaround that forces a Mac to always connect using SMB1. That method requires a bit of command line voodoo, which is described in full on his site.

Know of a better Mavericks SMB2 connection workaround or even a fix? Share it and a link in the comments below…

Related Posts:
OS X Mavericks Dropping Apple Filing Protocol
New in OS X Mavericks: OpenGL 4.1 Brings Features, Performance
OS X Mavericks on an Original Mac Pro
Can My Mac Run OS X 10.9 Mavericks
How To: Force Empty Trash in OS X Mavericks
Ava, Allison: New Voices in OS X 10.9
Enhanced Dictation in OS X 10.9 Mavericks
What’s New in OS X 10.9 Mavericks

2 Comments »

  • Steve Dibb said:

    If you’re using Samba, you can set ‘max protocol = NT1′ in the [global] section of smb.conf.

    You can verify it’s setup correctly by running ‘testparm -sv | grep protocol’.

    See https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html for reference, section “client max protocol (G)”.

  • jackmstarr said:

    I struggled with this until the addition of a time capsule forced my hand. Everything (2 iMacs, 2 MacBook Pros, and a couple of windows computers * for wife’s work * plus a couple of iPads, an iPhone, and iPod touch) were on 192.168.x network.

    I could mount a share from the Ubuntu black box, until I tried to access it. Error messages abounded in the logs.

    putting the 10.0 network for all the Apple stuff made it easy! They all see each other, and the Ubuntu share w/o a hitch! Fear not the 10 dot!

Leave your response!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.