Koozali.org: home of the SME Server
Contribs.org Forums => General Discussion => Topic started by: morpheus on May 16, 2017, 12:03:04 PM
-
G'day, business has added a couple of Mac desktops and laptops much to my dismay. I have spent a long time trying to find how to allow the Macs to access the file-sharing system. Could find nothing in Documentation to assist me (plenty on Windows connections, setup). So I would humbly suggest that a section be added to Chapter 7 configuring the computers on your network to give a quick reference to the procedure to allow the Mac OSX users to map the shared folders and access them.
I am still to test the following:
Finder->Go->Connect to Server
Enter the following: smb://[server-ip]/[share-name],
Enter sme-server username and password
Connect
If this is not the correct procedure, please correct. If I have posted in wrong place, please move to appropriate place.
-
This is a good suggestion.
Google night give you few results including http://osxdaily.com/2013/10/30/connect-smb-nas-network-shares-os-x-mavericks/
Would you be able to write something for us to include with some pictures and reference to the os version?
-
Thanks for the link as this issue has been very irritating. I will check the use of cifs instead of smb tomorrow, and if it works I will write up my notes to include in the appropriate manual section.
-
My Macbook Air running El Capitan (10.11) "sees" my SME 9 server in Finder.
- Open Finder
- "show" (expand) 'Shared'
- Locate the hostname of the SME server
- Click on it
- enter SME user and password when prompted
I now get two shares in Finder - 'Primary', and the share belonging to the user whose account I used to login.
The 'Primary' share shows me the contents of /home/e-smith/files/ibays/Primary/
The user share shows me the contents of /home/e-smith/files/users/mmccarn/home
I have made no customizations to the SMB portions of my SME, and I don't have it configured as an active directory controller.
-
So simple and stupid, no tricks ?
Great to hear
-
using cifs://[ip address] instead of smb://[ip address] solved my issues.
-
You'd never use the IP address
Use the FQDN of your server