SMB Problems solved in Mavericks with a NAS

So, I’ve recently been using a QNAP NAS, and it’s been working great on Windows computers. However, when it comes to using it on the network with the Mac in Mavericks, performance is extremely poor.

I have found this post, and I am only reposting it because I’ve found a solution, and just in case the other blog disappears, then here is a record of it.

This is a direct rip from here and I take no responsibility for it: http://cammodude.blogspot.com/2013/10/os-x-109-mavericks-workaround-for-smb.html

 

OS X 10.9 Mavericks Workaround for SMB

Upgrading is never easy.  There is always some new bug introduced as a feature.  That said, you may have noticed that connecting to NAS shares worked perfectly in OS X 10.8.x but doesn’t anymore in OS X 10.9 (Mavericks).   Here’s the lowdown:DISCLAIMER:  Though these are pretty harmless changes, any changes you make are at your own risk. 

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 Option 1:

To force your connection to be SMB1, simply type cifs://servername instead of smb://servername when connecting to a Windows or NAS share.  This is by far easier and requires no real configuration changes.

Workaround Option 2:
To force all connections to be SMB1:
  1. Open A terminal window
  2. paste in the following line followed by the return key(should be all on one line):

echo “[default]” >> ~/Library/Preferences/nsmb.conf; echo “smb_neg=smb1_only” >> ~/Library/Preferences/nsmb.conf

What the command does:
  1. Creates a file called nsmb.conf  in your  home directory at the path ~/Library/Preferences/nsmb.conf.
  2. Adds directives to force SMB connections to use the SMB1 protocol.  This is slower but stable.
How to remove the workaround:
  1. Open a terminal window
  2. paste in the following at the prompt and then hit the return button:
rm ~/Library/Preferences/nsmb.confNotes:

Its a good idea to restart your mac before trying to connect to your storage again. This will clear any hung SMB processes from previous attempts to connect to your storage before implementing this workaround.

 

 

UPDATE:

I also want to sugguest what NOT to install if you are using Mavericks.

Do not install SMBUp. I looks great and promises good things, and looked at it and thought, “yeah, that looks great!” So I installed it. Oops. Wrong option. It stopped the shared networking working properly in the OS X environment, to where I couldn’t see any computers except those issuing alerts via Bonjour. The stupid thing was, I was could see all the computers on the Windows XP virtual machine, but not the Mac.

So, because I did install it, I (finally) fixed the problems that SMBUp caused. This post has the answers. The one by SirGrumpy and following will help you. Enjoy! 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at WordPress.com.

Up ↑

%d bloggers like this: