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
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:
- Open A terminal window
- 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
- Creates a file called nsmb.conf in your home directory at the path ~/Library/Preferences/nsmb.conf.
- Adds directives to force SMB connections to use the SMB1 protocol. This is slower but stable.
- Open a terminal window
- paste in the following at the prompt and then hit the return button:
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.
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! 🙂