Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.9: Switch the SMB stack to use SMB1 as default System 10.9
The new SMB2 stack deliverd with OS X 10.9 (Mavericks) often fails to connect to NAS devices or behaves strangely on server volumes, such as an inability to change file/folder names.

Some possible workarounds are:

First try using cifs:// instead of smb:// to connect to the server volumes.

If that doesn't help, then there is a way to change all connections that use SMB1 by entering this command in Terminal:
echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf
To restore the default SMB2 you simply need to delete the newly created configuration file (nsmb.conf) with the command:
rm ~/Library/Preferences/nsmb.conf
Both workarounds force OS X to use SMB1 as a network protocol instead of the default SMB2 used by OS X 10.9 (Mavericks). While the first is an ad hoc solution the second is a persistent but reversible configuration change (for this user account). SMB1 is slower than SMB2 but stable.

[crarko adds: I don't have a way to test this at the moment, but I do recall reading that people have experienced some of these issues. If someone has a NAS device to test this with (especially if there have been problems) please let us know if either of these fixes helped.]
    •    
  • Currently 2.18 / 5
  You rated: 2 / 5 (17 votes cast)
 
[37,305 views]  

Hint Options


10.9: Switch the SMB stack to use SMB1 as default | 12 comments | Create New Account
Click here to return to the '10.9: Switch the SMB stack to use SMB1 as default' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.9: Switch the SMB stack to use SMB1 as default
Authored by: benwiggy on Dec 03, '13 07:31:48AM

I thought the whole point of using SMB2 was for more stable connectivity than previously!



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: ShadowBottle on Dec 03, '13 07:48:22AM

You'd think!



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: tkothe on Dec 03, '13 01:20:35PM

Do I need to restart or log out and back in after the changes? I have problems COPYING files to my SMB share since Mavericks! It won't let me copy because Finder tells me the files are still in use. Yes, that's COPYING (i.e. READING from the source, not moving, i.e. writing). This is ridiculous and Windows-like stupidity. Makes me want to go back to Linux...



[ Reply to This | # ]
No, a restart isn't required. [n/t]
Authored by: MacParc on Dec 19, '13 03:32:03AM

The changes take effect immediately (but of course you need to reconnect after switching to SMB1).



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: dfbills on Dec 04, '13 05:09:02AM

If you have issues with "busy" files, try browsing in a view other than column view. I've found that the previews generated by the Finder in this view very often lead to "busy" files that cannot be easily cleared.

---
-d



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: ms_t_rie on Dec 04, '13 10:51:44AM

It's probably the preview pane that would be causing it then. I use column view all the time, but I have the preview pane unchecked. I'm finding 10.9 to be faster and more stable than 10.8, sometimes on 10.8, finder would revert to the root instead of the previous folder when I was deleting stuff, it works great in 10.9. I use smb://(server) to connect to our old Buffalo NAS.



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: hypert on Dec 05, '13 09:13:57AM

I never use the preview pane (yes, really!), and I run into this all the time in Mavericks, copying files from the local HDD to a NAS. Has this fixed the problem for other NAS users?



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: hypert on Jan 05, '14 05:54:07PM

Finally bit the bullet and tried this. The performance difference on my system is amazing! Mid-2010 Mac mini running Mavericks, using Graphic Converter to browse photos on an Iomega NAS (connected via Ethernet to the same switch the Mac is using). Original performance was so poor that I copied photos to the local drive for browsing, instead of using the NAS! Made the change listed here today, and using GC to browse the NAS feels just as fast as the local drive!

Thanks for the terrific hint!



[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: tkothe on Dec 16, '13 12:16:14AM

I also never user preview pane or the column view at all. I use list view 99% of the time.

It's still a pain.

How can I find out if my share is really mounted using v1 ? It does not seem that way.
mount on the command line tells me just "smbfs".



[ Reply to This | # ]
Addendum: Switch the SMB stack to use SMB1 as default for all users
Authored by: MacParc on Dec 19, '13 12:55:55AM
There's also a possibility to change all connections to use SMB1 system-wide (for all users) by entering this command in Terminal:

sudo sh -c "echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb1_only' >> /etc/nsmb.conf"


To restore the default SMB2 you simply need to delete the newly created configuration file (nsmb.conf) with the command:

sudo rm /etc/nsmb.conf


[ Reply to This | # ]
Addendum #2: SMBconf for OS X 10.9 (Mavericks)
Authored by: MacParc on Mar 20, '14 03:07:46AM

For those who don't like Terminal.app there's a small, free app based on my hint:

SMBconf

[ Reply to This | # ]
10.9: Switch the SMB stack to use SMB1 as default
Authored by: wiggytoo on Jun 19, '14 11:15:23AM

Thanks for this information which I found when trying to solve a problem saving .DOCX files from Office for Mac 2011 to file shares on a Windows Server 2012.

There was also a possible hint from http://word.mvps.org/Mac/CantSaveToServer.html which I'd also tried.

In the end I believe the issue lies with and incompatibility between AVG Anti Virus for Mac (and its real time protection), Office 2011 for Mac and Windows Server, turning this off seemed to solve the problem - more testing required.

I probably should have disabled AV first.



[ Reply to This | # ]