Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Can't Connect to SMB in macOS 10.12?

Status
Not open for further replies.
Joined
Jan 5, 2017
Messages
1
Hi, everyone,
I just upgraded my FreeNAS to 9.10 so as to take advantage of the features in the newer version of Samba that allegedly lets Final Cut Pro store its library over SMB. However, while I can get AFP to work just fine with the Mac, I can't connect to the SMB shares.

In both cases, I have guest access disabled. I created a user account on FreeNAS and can authenticate just fine to it when using AFP. However, once Finder sees that SMB is available, it now (tries) to default to that (as it should in newer macOS releases). However, sometimes when I click on my server's entry in Finder, it says "Connection Failed" and hitting "Connect As..." says:

There was a problem connecting to the server "beatrice".
Check the server name or IP address, then try again. If you continue to have problems, contact your system administrator.
At other times, the SMB share has been listed but when I try to load it, it says:

The operation can't be completed because the original item for "Photo_Vault" can't be found."​

I don't see anything amiss in my settings, but can you point me in the right direction of where to even begin debugging this.

Incidentally: Zeroconf seems to be working fine, like I said, when I turn off SMB and use AFP, Finder connects just fine; additionally, if I try to connect directly to 192.168.1.30, it fails just the same as using the Zeroconf entry. I can access the other network services on the FreeNAS just fine (web admin interface), AFP, etc., whether I use "beatrice.local" or the IP address.

Thanks for your help!

Best,
Tim
 
D

dlavigne

Guest
Were you able to resolve this? If not, which VFS objects are enabled on the SMB share?
 

m0nkey_

Dedicated Sage
Joined
Oct 27, 2015
Messages
2,732
This is a common problem.

Can you connect in Finder using Command-K and typing in the server share address? e.g. smb://freenas/share
 

mrembetsy

Junior Member
Joined
Nov 18, 2015
Messages
16
I have the same issue with FCP X and smb shares. I can connect just find over my mac, the issue is either with my samba setup, or fcp x. I have enabled the vfs objects and restarted smb according to https://support.apple.com/en-us/HT207128. Samba on 9.10 is more than new enough to satisfy their requirement there. thoughts?
 

Xplitz

Junior Member
Joined
May 14, 2015
Messages
16
Me too I have the same problem! I searched the forums and found this, I don't want to spam the forum(Well I don't literally spam just want to avoid duplicate posts). I can't connect to SMB using Mac OS, sharing with AFP is fine. Can you share both SMB and AFP at once? I hope we get answers to this problem. Thank you OP and friends!
-Vincent
 

mrembetsy

Junior Member
Joined
Nov 18, 2015
Messages
16
yes you can have multiple shares, AFP, SMB, NFS, etc. they are different protocols and shouldn't have an issue on the same shares. I have also tried only SMB on my FCP X directory but nada. So I am stuck too.
 

m0nkey_

Dedicated Sage
Joined
Oct 27, 2015
Messages
2,732
yes you can have multiple shares, AFP, SMB, NFS, etc. they are different protocols and shouldn't have an issue on the same shares. I have also tried only SMB on my FCP X directory but nada. So I am stuck too.
Don't do this. One share per dataset, otherwise you'll get some weird file locking issues when being accessed over different protocols.

This is covered in the documentation: http://doc.freenas.org/9.10/sharing.html
It is generally a mistake to share a volume or dataset with more than one share type or access method. Different types of shares and services use different file locking methods. For example, if the same volume is configured to use both NFS and FTP, NFS will lock a file for editing by an NFS user, but a FTP user can simultaneously edit or delete that file. This results in lost edits and confused users. Another example: if a volume is configured for both AFP and SMB, Windows users can be confused by the “extra” filenames used by Mac files and delete them. This corrupts the files on the AFP share. Pick the one type of share or service that makes the most sense for the types of clients accessing that volume, and use that single type of share or service. To support multiple types of shares, divide the volume into datasets and use one dataset per share.
 

mrembetsy

Junior Member
Joined
Nov 18, 2015
Messages
16
valid point. I have never had an issue with locking but then again docs are totally right. thanks for pointing it out. Just to clarify I am not doing this myself, my AFP is for my time machine, the rest (nfs, smb) are on separate shares. Thanks for catching my misinformation.
 
Status
Not open for further replies.
Top