Automounting shares as guest

I'm trying to automount a share at boot time. It needs to be accessible to all users so I want to mount it using guest access. I can successfully mount the share as guest from the Finder so I know the server side is ok. I put the following line in /etc/fstab:
server:/share x url net,automounted,url==afp://guest:@server.local/Share 0 0
But when I try to access the share I get an authentication error:
[mac:~] user% ls /Network/Servers/server/Share/
ls: : Authentication error
Does anyone know how to make this work?

Similar Messages

Automount share point

How do I automount share points for users that aren't home folders? I'm trying to do it by making a group, and having the home folder for the group automount, because I want all members of the group to be able to have this share point automounted, but I've only been able to get it to automount the actual "Groups" share point. It also automounts the "Users" share point as well, which is undesirable, and I can't seem to figure out how to make it stop. I'll read up on it some more I guess.

Does this page contain anything useful?
(15711)

How do I get automounting share points with to appear on user's computers?

I recently purchased Sever 10.6, and upgraded to 10.6.8. I'm running it on a 2006 MacBook Pro with 4GB (only 3GB are addressed on this model). I really only need it for one thing: to serve 4 external drives to my home network. But I can't do this: I want to set up automounting share points with custom paths so that on login the disks appear on the user's desktop and/or in the sidebar. Clients range from 10.6.8 to 10.8.x to 10.9.x.
I've tried setting the sharepoints. I don't know what to put in for a custom path; trial and error has gotten me nothing. I don't want home directories, libraries or application folders - I just want those disks shared to computers on my network.
The little manual that comes with it is not helpful. If there's a written document somewhere that is specific about this, I'd be happy to just read it myself.
Thanks!
Sean

Hi Sean Hayes1,
Volumes, including server volumes, that mount at startup are controlled on the client computer using System Preferences > Users & Groups > Login Items. The preference pane says this is for applications you want to launch at startup, but it also works for network mounts. See this article -
OS X Mavericks: Login Items pane of Users & Groups preferences
http://support.apple.com/kb/PH14413
To add a new volume -
To have an item open automatically at login, click Add (+), then select the item.
Thanks for using Apple Support Communities.
Best,
Brett L

Automount Share points not showing up?

So I've got a Share point named 'Documents', 'Enable automount' is check and it has a custom path of '/Network/Documents'. (BTW, is the appropriate place for that?)
When I log in as a user I can see that the directory '/Network/Documents' is being created (by clicking on 'All...' in the finder sidebar), but nothing useful is happening with it... double-clicking on it takes me into the folder about 0.5 to 1 second then "redirects" me back to the 'Network' folder.
I don't get usable icons (on the desktop) for the 'Documents' share until I go Shared > MyServer > Documents ... only then do I see the share point in any sort of usable state.
Am I missing something? I assumed that making something automount would place it on the desktop or the sidebar or something when the user logs in.

+I assumed that making something automount would place it on the desktop or the sidebar or something when the user logs in.+
No. An automount only works if your server is configured to host a shared LDAP domain (OD Master) and the client is bound to that domain (so that it can read the mount record).
With that said, there are two types of automounts available via AFP:
*A Dynamic Automount*, which is typically used for the home directory share point(s). Dynamic mounts "eject" and remount as the user who is logging in at login time. The mount path is configured automatically in /Network/Servers.
For example, a share point configured to automount (located at /Volumes/Data/Homes on the server with name myserver.myco.lan) will dynamically automount at this path on the client:
/Network/Servers/myserver.myco.lan/Volumes/Data/Homes
*A Static Automount*, which is typically used for sharing common files; a shared Library is an example. Static automounts mount at /Network/mountname, and are done at startup time. Generally speaking, these will only work if one of the following is true:
1. AFP Guest access is on for the share point being statically automounted. (Make sure that AFP guest access is on for the AFP service and on for the share point. Disable it for any other share points that don't need AFP guest access.) In this case, the automount will be mounted as the AFP guest user, not the currently logged-in or connected user.
2. The client system is bound to an Open Directory Master via directory binding, and Kerberos is working properly on the master. In this case, the static automount will mount as the logged-in user.
If you just want to make a share point mount automatically at login time, consider adding the AFP share point's URL to the user's login items instead of creating an automount. This will mount the share point in the "classic" manner, where it appears in the Computer window and on the Desktop.
To do so, you can manage the login items (loginwindow.plist or com.apple.loginitems.plist) for the user or group via Workgroup Manager. Open TextEdit (for example), and type the URL for connecting to the share point - afp://myserver.myco.lan/stuff, for example - and drag that text onto the Desktop to create an AFP Internet Location file. Then drag that file into the login items section of Workgroup Manager to add it.
If your server has Kerberos running, you're set. When a client logs in, he/she gets a Kerberos TGT from the KDC and a service ticket for AFP which mounts the share point; no name and password to re-enter. If not, you can check the "connect with user's name and password" box in the login items section of Workgroup Manager to have login window hold the user's name and password temporarily and enter it for him/her.
Also note that Leopard clients don't automatically show mounted share points on the Desktop (but they do appear in the Computer window of the Finder and in the SHARED section of the sidebar). If you'd prefer to have users see shares on the Desktop again, you can manage that via Workgroup Manager's Finder preferences section.
Hope this helps!
--Gerrit
Message was edited by: Gerrit DeWitt

Windows 8 user cannot connect to public OS X Lion share as Guest, keeps asking for a password even though the folder is public?

As title suggests...
OS X Mountain Lion public share works fine for Mac's but as a guest from Windows its adamant it wants a password. If I use proper credentials it will allow me in the public share from the windows PC but I dont want to add creditinatials it should be an open folder to Network (LAN) WORKGROUP users.
OS X Guest account is set to "allow guests to connect to shared folders"
The Public folder is set in "Sharing" as READ ONLY everyone.
Mac's can access the share without needing credentials.
Windows PC asks for Username and Pass (have tried Guest (no password) or just pressing enter (no details)
Searched these forums see a few other people with similar problems yet no Answers
Help please!!

Try this on your PC:
Start->Run...->Open:\\<ipadressofyourmac>\<sharename>
You will be prompted for your username and password.
Or
'My Computer'->'Tools'->'Map network drive...'
enter:
\\<ipadressofyourmac>\<sharename>
in the 'Folder' field.
Click 'Connect using a _different user name_.'.
Enter your server username and password.
Click 'OK'.
Click 'Finish'.

Automounting shares

Ok, I realize this should be really easy, but does anyone know how I can have share points auto-mount on client machines? In setting up my new server, I've got the groups and users pretty well sussed out, and even have the machines logging in via the server, but I can't quite figure out what I'm doing wrong here.
I've set the sharepoints to be seen by the appropriate users and groups, and I can connect to them on the network from various machines. But selecting "Enable Automount" for the volumes in Server Admin doesn't seem to work. I'm sure I'm doing something wrong.
For the protocol, I'm choosing AFP (not sure what this'll mean for the Win boxes), and a custom mount path of /Volumes/share name. I'm guessing this is wrong? None of the other options seems correct.
And now, for some reason, none of the machines will even SEE /Volumes. I've had to take them off the directory.
This is on a Mac Mini with OS X Server 10.6.4, BTW. And yes, I'm a total n00b to OS X Server.

"I've set the sharepoints to be seen by the appropriate users and groups, and I can connect to them on the network from various machines. But selecting "Enable Automount" for the volumes in Server Admin doesn't seem to work. I'm sure I'm doing something wrong."
What exactly do you mean by "can connect...from various machines" and "doesn't seem to work"? You set up the Enable Automount and I'm assuming you gave them proper permissions. If that's all good, then it seems like it should be working to me. When you open up the finder, is anything showing up there? Or at least, did it at one point, as I noticed you said later they're not seeing them now (unless they're not seeing ANYTHING in /Volumes, which seems like a major problem to me since even your local HDs should be there...)?
I don't know as the actual mount path you choose really makes much of a difference other than where the client shows it being connected at, but I could be wrong (I've never noticed any issues regardless of what I chose for that).
Now, if you're able to get to the share point by going through the finder but simply want them to show up on the dock, that needs to be set up in WGM in the Login and Dock prefs (someone else will need to give specifics for this, since I'm not at my server until prob Tues and don't remember the exact details off the top of my head). Come to think of it, you may need to set it up in the Login section anyway, which may be your problem (not 100%, since I've always done all 3 points--set up in Server Admin, and both Login and Dock prefs in WGM). Basically, use WGM on a client machine and add the share point into the "Items" section in the Login prefs and check the Authenticate with user's login (or something to that effect--first checkbox there), but that's all I remember explicitly without looking at mine for more exact syntax.
For the AFP thing for your Windows machines, it'll probably be as simple as turning on the SMB protocol to allow them access, but you'll probably want to get the AFP connected sorted out first anyway.
Message was edited by: Rikakiah

VirtualBox: How to share a guest's (XP) internet with the host (OS X)

I have an internet connection that can only be used on Windows operating systems (our school requires that we install an .exe login client to connect to the dorm internet). As I am currently using a Mac, my goal is to get the internet running in XP in a virtual machine, and then share the virtual machine's internet with the host. Here's what I've done so far (I'm pretty new to all this, so sorry if I leave out anything important!):
1) Install VirtualBox, create a new XP virtual machine
2) Add a Bridged Adaptor NIC to the guest allowing it access to the ethernet port
With this, I can use the internet fine in the guest, but have no internet in the host. (Note: Making the NIC NAT does not work. When set to NAT, the login client in XP can't find the school's server and I can't use the internet). The next step is getting the guest to share it's internet with the host. Here's what I've tried:
3) Add a second Host-only Adaptor NIC to the guest specifying the following:
IP: 192.168.22.2
Network Mask: 225.225.225.0
DHCP Server unclicked (disabled)
4) In the guest, enable Internet Connection Sharing for the internet connection.
At this point, LAN 2 in the guest (the connection to the host, I think) gets automatically configured with an IP of 192.168.22.1 and the same mask as above. Back in the host, I can ping 192.168.22.1 and get a response. But no internet.
I feel like I'm missing a step, namely how do I instruct the OS X host to use the Host-only connection as its internet connection? I can see the connection ("vboxnet0") when I use ifconfig in the terminal but I have no idea how to use the connection for internet. Anyone know how I can do this?
Thanks for your help!

OS X is passing the Internet connection to the guest OS, it doesn't work the other way around.
You will have to install Windows into Bootcamp and I don't think XP is supported any longer, however Win 7 Pro+ will run most XP programs.
Windows in BootCamp or Virtual Machine?
You'll of course be booting the Mac directly into Windows and thus OS X won't be running, thus you can't share the Internet connection to OS X.
Another alternative is to use a Windows 7 Pro+ machine to connect to the network and then sharing it's Internet connection to the Mac via Ethernet cable or wirelessly.

Systemd 215-4 breaks automount shares

Hi,
I use systemd automount feature to mount samba shares at boot with the following entry in /etc/fstab :
//nas/partage /home/hubert/nas cifs noauto,x-systemd.automount,x-systemd.device-timeout=10,credentials=/home/hubert/.smbcredentials 0 0
This worked fine until I upgraded to systemd-215-4.
Now, automount fails with the following error :
systemd[1]: home-hubert-nas.mount mount process exited, code=exited status=32
Downgrading to systemd 214-2 solves the mount problem, but on shutdown, a 90s timeout occurs on unmounting with the following message : "A stop job is running for /home/hubert/nas
Any idea ?

After some digging, I answer to myself :
The "mount" issue has been declared on bugzilla bug #81529 and a workaround is also described by the author (thanks)
The "unmount" issue occurs only for network shares and Wifi network connection (unmounting network share is ok on wired connection)

How do you share a Guest's file to the owner's files - detailed instructions needed

Previously I asked how to save a file created by a Guest user into the owner's files. Matt Clifton answered "Put files in the Users/Shared folder, they will not be deleted when guest signs out."
I can't see how to do that. I am creating a recording on Microwave-Lite App and want to save it in my owner's files. I don't see a Users/Shared folder in Guest
or if it is to be done in Owner I don' know how to do that.
Any help would be appreciated.
thanks

Open the Owner's User folder, in it should be a folder called "Public". Inside the Public folder is a folder called "Drop Box." You should be able to drop files into "Drop Box" (though you can't open the folder).

Does or will the Airport Extreme be able to share the Guest network to a Ethernet port?

Did not know if there was or possibly will be the ability to seperate ethernet ports to make a hardwired guest network?

Sorry, not possible to extend the Guest Network using either wireless or Ethernet.
You might want to let Apple know on any new features that you want to see.
Apple - AirPort Extreme - Feedback

Trying to Get Netwrok Users Working in a Prelude to Portable Home User

Hi,
Currently the standalone server has 5 local client side users. I have created another user in WGM who has a network home folder. I can't log into him. The only other network user I have is the serveradmin, setup at the start of the process, which I can log onto with now problem.
The network user home folder is on a AFP automount share with guest access. I went to "home" on WGM and selected the AFP path (which is less than 83 characters) and successfully created the home folder. (I don't know if it is relevent but two other attemts at making home directories are still selectable in the home list, even though they no loger exist. In fact they still come up in the finder if I goto network/servers/myserver.company.co.uk/Volumes/).
My login screen is meant to show network users (having set the preference in WGM for my Mac), but only shows my local account, gueest and other. When I try to log on with the network user, it just shakes.
I did create a local account for this user, bound the account to the network account. The home folder automount didn't mount. When I manually mounted it the user's directory was there but with no access to the folders. I then noticed that if I logged into one local account the second local account I logged into would not show he server as a shared computer via AFP in the Finder (SMB showed up fine).
I suspect that I've set something up odd, but I am suspicious of the AFP automount. Any ideas?
Thanks,
Francis.

Thank you David & Jeff for responding.
To David - I had setup my new user as described by the documents and by you (i.e. Created user, made a "User" sharepoint with automount set as AFP "User Home Folders", used WGM to select this share for said user and created folder). The users homefolder can be seen under the share "Users". If I create a locally managed user on a client Mac and link it with this user, I can navigate to the folder under the "My Server" directory. What I wanted to do, and believe can do, is have this user as a network account, not a local one, with its home folder mapped automounting (which I thought meant that I could go to the relevant folders by using the standard icon's on the Finder - am I wrong? will I always need to go My Server>Users>username?).
To Jeff - this is the output:
Primary address = 192.168.0.2
Current HostName = myserver.mycompany.co.uk
DNS HostName = myserver.mycompany.co.uk
The names match. There is nothing to change.
I have set WGM for this computer to show network accounts on the login screen. It doesn't show the user I'm trying to setup.
Many thanks in advance for your thoughts.

Custom NFS share point directory showing up on all network machines

Hi,
I'm in the process of migrating our 10.4 PowerMac server to a Mac Pro (running 10.5). I've been trying to recreate our 10.4 server setup as much as possible and so far I've only come across one annoying issue.
We have fink installed on the server and under our 10.4 setup the /sw directory was set up as an NFS automounted share point with a custom mount point of '/sw'. I.e. users logging into client machines saw a /sw directory and could work with that. This made it easier to add fink packages as I only needed to do this on one machine (the server). This setup worked very well under 10.4 and had been working stably for the last couple of years.
As we now have (for another month or two at least) a mix of intel and Power PC machines, I don't want to share out the (intel) server version of fink to all clients. In Server Admin, I have chosen to set the NFS protocol options to specify the IP address of just one client (an intel machine). I am only using NFS to share this directory. The plan is to add more client IP addresses as we get more intel machines.
This works for the one intel client machine. Logging in via the GUI or via ssh allows you to run programs located under the /sw directory. The problem is that a phantom /sw directory appears on all client machines, even though their IP addresses are not specified in Server Admin. The /sw directory has root/wheel permissions (for user/group) and attempting to list its contents returns 'Operation not permitted' (even with 'sudo ls /sw').
If I use Directory Utility to remove the connection to the Directory server on our main server, then the /sw directory becomes owned by root/admin and I can remove it (it appears empty). Reconnecting to the Directory Server changes the permissions back to root/wheel. It is also worth noting that when I first installed fink on the server (in /sw) the act of making this a share point also changed the permissions on /sw to root/wheel meaning that I couldn't access the fink programs that I had only just installed (this forced me to reinstall fink in /Volumes/Data/fink).
Has anyone else noticed this behavior? It almost seems like Server Admin is not honoring the list of IP addresses that are being listed as targets for client machines. I had planned to install fink locally on the PowerPC clients until we upgrade them to intel machines. However, I would then also have to install fink somewhere other than /sw as I can't write to that directory. I would presume that this behavior should happen on any NFS share point that is trying to automount to a custom mount point on a client. Can anyone else verify this?
Regards,
Keith

As a footnote. I have now removed my shared fink installation. It is no longer listed as an NFS sharepoint in Server Admin and running the 'showmount -e' command does not list it. However, a /sw directory is still being created on the server and on the client machines on our network.
This is perplexing and frustrating. There is no sharepoint any more. I rebooted the server but it makes no difference. I removed the /sw directory (on the server) by booting the machine in target firewire mode and removing it by using a 2nd machine. But following the restart, it appeared again.
This suggests that once you make any custom mountpoint (using NFS sharing) then you will forever be stuck with a directory at the root level of all your clients which you can not remove.
Keith

NEtwork Home folders not working--automount failure?

Hi,
I've been running an OS X Server 10.4.2 server for several months without a problem. This morning I came in to find none of the clients able to log into their network user accounts.
Sure enough, login window indicated "network accounts unavailable". I logged into a local user on several clients, and found the automount share point with the user directories was not available.
I attempted to unbind, then bind via Directory Access without success. Directory access apears to register the computer, even warns that a record for each computer already exists, but will not load the share point even after a restart.
I've toggled the automount on and off via WorkGroup manager to no avail. The server is still on the network, it gets an internet connection, and can be logged into via File SHaring without problem--just the automount share point with the network user account info fails to work as it has been.
Suggestions would be GREATLY appreciated.
-David

Well, I was getting fairly frustrated with the down time so I backed up the user accounts and did an erase&install of Mac OS X Server 10.4.7.
I reconfigured the server and still no automounting sharepoints on the clients. I can only log into the network accounts from the server--locally from the server, that is.
I am becoming fairly bewildered at this point...

[solved] Can't connect to samba shares

This is probably my fault, but for the life of me I can't figure this out. I started out trying to get usershares to work by following the wiki at https://wiki.archlinux.org/index.php/samba, and I am unable to connect to the resulting shares either from the local host or from my netbook. It tells me permission denied. I then tried creating a public share with guest access, because I couldn't get the usershares to work. I am unable to get that working either. I have
chmod 777 -R
the folder I am sharing, as well as the
/var/lib/samba/usershare
folder. Please help. Here is my smb.conf:
#======================= Global Settings =====================================
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
hosts allow = 192.168.1. 127.
log file = /var/log/samba/%m.log
max log size = 50
security = user
map to guest = Bad User
guest account = nobody
dns proxy = no
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = Yes
usershare owner only = False
#============================ Share Definitions ==============================
[Bleach]
path = /mnt/Data/Bleach
read only = no
guest ok = yes
I tried adding the nobody user since there was no users listed when running
pdbedit -L
using
pdbedit -a -u nobody
and just pressed enter for the password field. This did not help.
testparm says
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Bleach]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
map to guest = Bad User
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = No
usershare path = /var/lib/samba/usershare
idmap config * : backend = tdb
hosts allow = 192.168.1., 127.
[Bleach]
path = /mnt/Data/Bleach
read only = No
guest ok = Yes
Last edited by mdshann (2014-03-04 06:01:04)

uninstalled samba, reinstalled it. deleted old config file. created new config with just the contents that the wiki states is necessary for usershares to work. the current smb.conf looks like
[global]
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = yes
usershare owner only = False
added my user to samba using
pdbedit -a -u mdshann
started smbd and nmbd and enabled both. tried to share a folder, caja says samba is not installed. use yaourt to search for caja and find package mate-file-manager-share. installed said package, killed and restarted caja. shared folder and told it to add permissions automatically. checked the boxes to allow guest and to allow users to change files. still I cannot connect. just for reference, I have used the wiki article sections from the beginning of the article through adding a user. I did not use the creating a share section as I want usershares to work through MATE and CAJA. It creates the share and it is visible on the network, I just can't connect to it.
Pretty much the same as what I tired before, with the same result. Only difference is I haven't tried manually creating the share through smb.conf, but that didn't work before either. No reason to think it will work now, the problem was the same whether I used the gui usershares option or adding the share to smb.conf.
I was able to get samba working with a very similar config file as in my first post, on arch based manjaro on my server at work. I did not enable or use usershares at work, but creating the shares in smb.conf worked just fine. Why will the same procedure not work on arch? Same packages for the most part, manjaro just adds a few. In fact, when I set up samba on manjaro, I used the arch wiki article, as Manjaro's wiki is sparse. Main reason we used manjaro at work was the speed of installation was much quicker, and we needed the machine back up quickly so we could start backing up our customers data. (I own a PC repair shop.)
On a side note, this community has served me well in the past the few times I have have issues since I started using arch 5 years ago. Why my post has gone so long without a reply other than being chastised for trying to call attention to a 3 day old unanswered thread is beyond me, but I am not thrilled by it. It has now been a full 2 weeks since my original post. I have never had this issue before, and if I can't bump or somehow call attention to my thread I am unsure of how to get help. Am I supposed to keep posting new threads on the same issue? I would think those would get closed rather quickly if I had. Should I post nonsense on this thread, I mean anything other than the word bump. A discussion of cat videos maybe?

SOME automounts not working

I have 7 shares publshed as automounts on a 10.4.8 server.
four of them will automount on clients, and 3 will not.. I can't seem to find anything different about the shares--the users trying to automount them all have permissions to do it, and will mount them when going to network/servername/CONNECT
The server with the shares is an OD master running kerberos, DNS, everything else works, etc etc etc, no issues there that I can tell. the errors on the clients look like this:
Feb 17 00:36:37 musicbox automount[332]: Can't mount darkstar.186.house:/Volumes/A-V/Captures on /private/var/automount/Network/Captures: Input/output error (5)
Feb 17 00:36:37 musicbox automount[332]: Attempt to mount /automount/static/Network/Captures returned 5 (Input/output error)
Feb 17 00:36:37 musicbox automount[197]: Can't mount darkstar.186.house:/Volumes/A-V/Captures on /private/var/automount/Network/Captures: Input/output error (5)
Feb 17 00:36:38 musicbox automount[333]: Can't mount darkstar.186.house:/Volumes/A-V/Downloads on /private/var/automount/Network/Downloads: Input/output error (5)
Feb 17 00:36:38 musicbox automount[333]: Attempt to mount /automount/static/Network/Downloads returned 5 (Input/output error)
Feb 17 00:36:38 musicbox automount[197]: Can't mount darkstar.186.house:/Volumes/A-V/Downloads on /private/var/automount/Network/Downloads: Input/output error (5)
Feb 17 00:36:38 musicbox automount[337]: Can't mount darkstar.186.house:/Volumes/A-V/DVDs on /private/var/automount/Network/DVDs: Input/output error (5)
Feb 17 00:36:38 musicbox automount[337]: Attempt to mount /automount/static/Network/DVDs returned 5 (Input/output error)
Feb 17 00:36:38 musicbox automount[197]: Can't mount darkstar.186.house:/Volumes/A-V/DVDs on /private/var/automount/Network/DVDs: Input/output error (5)
why would it be picking on these three shares?
TIA

I've seen the exact same message. I would consider reducing the number of automount shares you have. You could have one automount share and simply include subfolders with appropriate permissions/ACL's for users and groups as you need. I've read somewhere that Apple recommends a very small number of automount shares (maybe 2 or 3). I can't remember where I saw this tidbit, but I've moved all stuff that needs to be in an automounted share to one share and no longer see the message.

Automounting shares as guest

Similar Messages

Maybe you are looking for