SMBconf
SMBconf
3.2

2.2

SMBconf free download for Mac

SMBconf

3.2
06 October 2018

Switches to SMB 1 on OS X 10.9 or later.

Overview

SMBconf switches to SMB 1 on OS X 10.9 or later. OS X 10.9 (Mavericks) brought SMB 2 as the default network protocol; with OS X 10.10 (Yosemite), SMB 3 was added. If you face issues connecting to your NAS, or connections to Windows file servers don't work as expected (e.g., inability to rename files or folders), it may help to switch back to the slower but more reliable SMB 1.

What's new in SMBconf

Version 3.2:
  • Added: compatibility with macOS 10.14 (Mojave)

Join over 500,000 subscribers.

Subscribe for our newsletter with best Mac offers from MacUpdate.

8 SMBconf Reviews

Rate this app:

tc31716
17 March 2016

Most helpful

I can confirm this works on El Capitan 10.11.2 My user had an issue with our Windows 2012 file server network share. After upgrading from Yosemite to El Capitan, she would connect to the server ok, open a bunch of subfolders, and frequently throughout the day, Finder would kick her back to the beginning shared folder. This forces her to open the subfolders again and again. Apple support suggested disjoining/rejoining domain, replacing profile, and recovering the OS. We did all but the last to no avail. SMBConf works just fine, she's on SMB1, and I will revisit the problem later if they come out with an update that fixes this problem.
Like (1)
Version 2.1
si458
10 October 2019
doesnt work on 10.14.6 Mojave, doesnt change /etc/nsmb.conf at all doesnt even touch this file at all
Like
Version 3.2
2 answer(s)
MacParc
MacParc
10 November 2019
It does work! The app touches ~/Library/Preferences/nsmb.conf !!!
Like
Version 3.2
MacParc
MacParc
10 November 2019
There's a ReadMe file which says: "SMBconf.app changes the default SMB protocol on the ACTUAL USER ACCOUNT to SMB 1 …"
Like
Version 3.2
mcpherson-jay
05 April 2018
Does not appear to make any difference for Windows connectivity to High Sierra... not one bit. Don't waste your time. Install SMBUp instead.
Like
Version 3.1
2 answer(s)
MacParc
MacParc
05 April 2018
You still didn't get the point: SMBup is server setup software and SMBconf sets the protocol version for clients. ;-)
It's a completely different type of software for a completely different task.
Like (1)
mcpherson-jay
mcpherson-jay
17 April 2018
Dear MacParc - of course! I had already figured this out by the time you posted. Would have deleted my comment if it was possible. Appreciate the clarification!
Like (1)
residelca
16 November 2016
This works in Sierra as well. I forced deleted the SMB-restriction Apple implemented in Sierra, due to the fact of a security bug in Windows. I could not connect to a Windows share anymore and Acrobat Distiller crashed. By installing/using this app, with SMB1 my connection and Distiller both work again.
Like (1)
Version 3.0
kengler412
30 October 2016
Doesn't connecting as cifs:// instead of smb:// do the same thing?
Like (1)
Version 3.0
2 answer(s)
MacParc
MacParc
30 October 2016
Yeah, that's correct and I indicated this in my hint, see the URL mentioned in the ReadMe file: http://hints.macworld.com/article.php?story=20131122083837447

(However when you create an alias of a server volume connected via cifs, it will use SMB 2 or 3 when you reconnect.)
Like (1)
kengler412
kengler412
31 October 2016
I see. Thanks.
Like (1)
tc31716
17 March 2016
I can confirm this works on El Capitan 10.11.2 My user had an issue with our Windows 2012 file server network share. After upgrading from Yosemite to El Capitan, she would connect to the server ok, open a bunch of subfolders, and frequently throughout the day, Finder would kick her back to the beginning shared folder. This forces her to open the subfolders again and again. Apple support suggested disjoining/rejoining domain, replacing profile, and recovering the OS. We did all but the last to no avail. SMBConf works just fine, she's on SMB1, and I will revisit the problem later if they come out with an update that fixes this problem.
Like (1)
Version 2.1
1 answer(s)
cmhjon
cmhjon
19 July 2016
OMG! I am having the EXACT same issue but it's with a Windows Server 2008r2 box. I've already implemented the fix shown here but using a different method. So it would seem it's an El Capitan issue???
Like
henkdevries-2
23 January 2015
Does anyones know if this helps with the 10.9 server SMB problems? so windows --> 10.9 server instead of 10.9 --> windows?
Like
Version 2.0.1
1 answer(s)
MacParc
MacParc
20 October 2015
No, this just works for Mac clients connecting to any kind of server.
Like
69number69
01 November 2014
Is this utility an alternative to SMBUp or something else?
Like
Version 2.0
1 answer(s)
MacParc
MacParc
02 November 2014
No. SMBUp lets you configure a Samba server.
SMBconf lets you chose the preferred network protocol.
Like (1)
Reddog99
01 November 2014
I'd like to rate it, but it doesn't do a stinkin' thing on my new Mini, running OS 10.10. It appears in the dock for about a half-second before disappearing; "nsmb.conf" not created...
Like
Version 2.0
1 answer(s)
MacParc
MacParc
01 November 2014
Maybe there are issues with permissions on your ~/Library directory.

Is there more info in the error message?
Like