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

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

  • 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?

    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?

  • 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

  • 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)

  • 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...

  • 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.

  • NFS / automount hangs on Solaris 10 SunOS oats 5.10 Generic_125100-07 sun4u

    We are running Solaris 10 125100-07 on a SunFire V440.
    We host computer services for another department on this host.
    The server acts as both an NFS server and an NFS client. We do a lot of cross-mounting in our environment due to the lack of large centralized storage.
    This particular machine automounts shares from our Solaris 8, 9 and 10 servers and possibly a few Suse servers, and a NetApp owned by another department.
    Every day and a half or so, something happens to either NFS or the automounter, and the machine 'hangs' in that we have NFS requests that never get filled.
    Restarting either autofs or the nfs client, or both does not seem to help. The only fix we have found so far is a reboot.
    We have throttled NFS_CLIENT_VERSMAX to 3 and set AUTOMOUNT_VERBOSE and AUTOMOUNTD_VERBOSE both to TRUE.
    The general failures we see look like this:
    May 17 04:44:15 oats nfs: [ID 333984 kern.notice] NFS server grieg not respondin
    g still trying
    May 17 04:44:15 oats last message repeated 1 time
    May 17 04:46:15 oats automountd[392]: [ID 196269 daemon.error] dupreq_nonidemp:
    duplicate request in progress
    May 17 04:49:57 oats last message repeated 4 times
    May 17 04:52:15 oats automountd[392]: [ID 196269 daemon.error] dupreq_nonidemp:
    duplicate request in progress
    The dupreq_nonidemp messages repeat until we reboot.
    The nfs server that does not respond varies from day to day. No other computer on our network complains about it.
    This started after we installed 125100-05, and has continued through 125100-07.
    As far as I can tell we are up to date on patches:
    root@oats # smpatch analyze
    No patches required.
    Any thoughts?
    I was thinking I might back out 125100-XX.
    dal
    e

    Interesting,
    we have the same problem on SunOS Generic_118833-36 on V440, V445, V240, V245, but not on an old E420, and not on a T2000.
    We upgraded them with patch cluster to Generic_138888-07, but it has not changed anything:
    E420 and T2000 are stable, the Fire-Vxxx have problem, each has its own "problem interval": one system 1.5 days, two systems 10 days, one every 3 months.
    The problem is: NFS/TCP is suddenly dead. Then all NFS mounts, e.g. a manual mount, is hung with "NFS server not responding". A reboot helps.
    We have added proto=udp to the mount options. No more problems since.
    Permanent mounts, without Automounter, would certainly work, too.
    But IMHO there is nothing wrong with Automounter itself, but the hanging occurs e.g. after 4000 NFS mounts, and Automounter is the enabler for that.

  • Unmount network share at sleep

    I would like to disconnect from my networkshare (unmount airdisk) when I put the Mac to sleep. Is there some setting or tool to do this automatically?
    Thanks

    I was waiting hoping for somebody else to answer, for as far as I know, this is a drawback that Macs have had for a long time!
    What I'd do myself I think, is make a Script in Automator, that unmounts the Share THEN puts Mac to sleep, rather than just trying to sleep it.
    It's not an Automount Share is it?
    Sorry, on Panther right now & no Airdisk to experiment with.

  • Export using QuickTime Conversion + SMB automount problems

    I have noticed an interesting (read bad) behavior in FCP (5.0.4) - If I try to do an export using quicktime conversion with the destination being an automounted (via netinfo) smb share as opposed to a apple-k mounted share in m4v, 3g, mp4, image sequence, still image or quicktime movie - I get a File Error: Unknown Folder. However if I do the same export but in avi, wmv, dv stream, or flc formats, it works fine.
    Trying to do the same export operation in quicktime pro produces an error -120, which is equivalent to directory not found.
    Seems like a quicktime problem dealing with the automounted shares, anyone else run into this issue? Have a fix?
    Thanks!
    C M I

    I know I can save locally + that it is tied to the quicktime components - I'm looking for fix/workaround that addresses the issue and streamlines my workflow, thats the reason I set up the automounter in the first place.
    So it's clear though, quicktime has no problem with smb in a general sense, it only has problems w/ the automounted smb shares - manual or command+k mounting of smb shares offer no problems.
    I use the automounting for two reasons: first is to emulate unc paths for rush render queue and second is to have consistent working paths to static content on a file server so final cut docs can be passed from editor to editor and link consistently.

  • Share Connect icon

    Share connect icon keeps popping up in my dock when I log in and I get an "connection failed" message. How can I stop message from appearing and icon from bouncing in my dock upon logging in?

    Hello, sounds like you have an Automount Share, I'd drag it off the Dock & replace with a Dynamic one...
    Mount that Share once, then once the Globe Icon shows up on the Desktop, drag that Globe Icon to the right side of the Dock between Applications & Trash. You now have a Dynamic Mount, a quick click on the Icon in the Dock will connect you.

  • Open Directory users can't access shares

    Greetings all.
    I apologize if this has been covered, but I couldn't find a search term that would locate the issue.
    I have a 10.5.8 Server running on a MDD dual 1Ghz G4. I have it set up as an OD Master and providing time services, DNS, file sharing, portable home directories and calendaring for a small workgroup of 7 computers. At least that's the idea when it's functional.
    It is behind a NAT and only serves the local network.
    Until I have the user's data all transferred from local directories to portable home directories, I need to make it so that the users can access the shares.
    In testing, when I try to access a share, I get an error message that the login failed because the username or password was invalid.
    However, when I go look at the Password Service log, the user was authenticated and in good standing.
    Any ideas?
    Thank you,
    John

    maybe some additional information or rephrasing might help.
    I have users and groups set up with ACLs on the shares that are set up with automount over NFS. The shares should also be available via appleshare, but not automount.
    The users are configured now with Portable Home Directories.
    The client computers are bound to the Open Directory Master on which the shares reside.
    The server runs network time services and the client computers use that for their time service.
    The server also runs DNS, and the client computers use that DNS.
    Users can log into their Portable Home Directories ok.
    Users can not log into shares via "connect to server" as it says that the username/password is invalid, even though the password service log says that the user was authenticated and in good standing.
    Users can see the NFS automount shares at /Network/Servers/Library (where it is supposed to be), but they cannot write, even though the ACL gives the user account permission to do so.
    For the permissions on the automount, I can't tell if the user is not being detected as the authenticated user, and is therefore being given "everyone" permissions, or if the ACL is not working on the mount and so the user is being given ""everyone" permissions.
    Anyone have any idea how I can find out?
    As to why a user can't log in via "connect to server" I'm clueless.
    Thank you,
    John

  • Open Directory authentication question

    I have 2 Apple servers.  One is running 10.6 (server), the other is running 10.5 (server).  I have my Open Directory on the 10.6 server, and I have the 10.5 server use it via LDAP for user authentication.  What I'd like to do is to assign a home directory on the 10.5 server for users in the 10.6 Open Directory.  Any ideas?

    mickey13 wrote:
    I have 2 Apple servers.  One is running 10.6 (server), the other is running 10.5 (server).  I have my Open Directory on the 10.6 server, and I have the 10.5 server use it via LDAP for user authentication.  What I'd like to do is to assign a home directory on the 10.5 server for users in the 10.6 Open Directory.  Any ideas?
    This should work the same way as normal.
    Define the user accounts in Open Directory as normal via Workgroup Manager
    On the 10.5 Server, set up a share point, usually AFP is used as the protocol, this is done in Server Admin
    On the 10.5 Server, set up that share point to be an Automounted share for user home directories, this will register that share in Open Directory assuming you have already successfully connected the 10.5 Server to Open Directory system, this is also done in Server Admin
    Go back to Workgroup Manager select a user account you want to store on the 10.5 server, click on the Home tab, you should now see the 10.5 share point listed as an available choice for storing home directories.
    Click on the 10.5 share point and save the user account.
    I normally now click on create Home directory, although this happens automatically when a user logs in for the first time.
    It is perfectly ok to mix 10.5 and 10.6 servers in this manner. The client machines can also be a different version e.g. 10.4
    What you are doing above even though you are mixing 10.5 and 10.6 servers, is the same as you would do to spread the workload of user home directories across multiple servers. While handling user home directories does not cause a massive amount of CPU activity (or memory use) it does cause a significant amount of disk activity and therefore at a certain level spreading user accounts across multiple servers is recommended.

Maybe you are looking for