We’ve just started to try to configure a new CentOS 7 disk server, and NFS seems OK so far, but I’m having problems with smb mounts to a Mac OS X client.
I have the [homes] section as usual, and some additional shares restricted to specific users, but none seem to work. I know I’m authenticating OK (both from the smbd logs and because when I type the wrong password the Mac’s behavior is different), but in no case can I see any files. The Mac gets as far as creating a mount point and opening a blank Finder window, but it’s completely empty, and when I try to select the server in the Finder sidebar it says “Connection failed” and shows a “Connect As” button, which just initiates another login/mount dialog window.
I don’t know what configuration bits are important, so I’m not sure what to include with this message. I do know that I have things set up very similarly to our previous CentOS 6 smb server, and that one seems to work fine.
If anyone has gotten such a configuration working, or has any suggestions as to what options in the smb.conf file to focus on, I’d appreciate any clues.
thanks, Noam
Only Mac clients are affected? Have you tested a Linux (e.g. Fedora 25 live OS would do) client?
It's necessary for all files to have selinux context system_u:object_r:samba_share_t:s0. You can either user chcon -R to apply it recursively to a particular directory you're sharing, or if it's an entire (dedicated) volume, you can apply it volume wide with a mount option, 'mount -o context="system_u:object_r:samba_share_t:s0" /dev/mapper/brick /brick'
I'm not doing anything different for my Mac client than for a Linux one, at least not that I'm aware of; however I'm using samba-4.5.3 since I'm using Fedora 25 server. It may be that older versions need to force a lower version of SMB depending on which Mac client you're using.
Chris Murphy
This is my smb.conf, it's extremely basic.
https://paste.fedoraproject.org/519466/34678791/
Note that max version is commented out. I've been using some version of Samba 4 for a little over a year, and with macOS versions 10.9 through 10.12.
Chris Murphy
On Jan 3, 2017, at 1:24 PM, Chris Murphy lists@colorremedies.com wrote:
Only Mac clients are affected? Have you tested a Linux (e.g. Fedora 25 live OS would do) client?
It's necessary for all files to have selinux context system_u:object_r:samba_share_t:s0. You can either user chcon -R to apply it recursively to a particular directory you're sharing, or if it's an entire (dedicated) volume, you can apply it volume wide with a mount option, 'mount -o context="system_u:object_r:samba_share_t:s0" /dev/mapper/brick /brick'
I'm not doing anything different for my Mac client than for a Linux one, at least not that I'm aware of; however I'm using samba-4.5.3 since I'm using Fedora 25 server. It may be that older versions need to force a lower version of SMB depending on which Mac client you're using.
Thanks. Given that my smb.conf is also pretty basic, it could certainly be SElinux. I’ll try your suggestions.
Noam
____________ || |U.S. NAVAL| |_RESEARCH_| LABORATORY Noam Bernstein, Ph.D. Center for Materials Physics and Technology U.S. Naval Research Laboratory T +1 202 404 8628 F +1 202 404 7546 https://www.nrl.navy.mil https://www.nrl.navy.mil/
On Jan 3, 2017, at 1:36 PM, Noam Bernstein noam.bernstein@nrl.navy.mil wrote:
Thanks. Given that my smb.conf is also pretty basic, it could certainly be SElinux. I’ll try your suggestions.
Cool - that worked. Giving SElinux appropriate context for the volume in questions did it. Thanks again.
Noam
-
Chris Murphy -
Noam Bernstein