10.8 fails to mount 10.5 shares

So I just installed 10.8 last night and right off I was alerted that it couldn't mount my media and backup shares that reside on a Mac Mini running 10.5. Is anyone else noticing issues mounting shares on Macs running anything lower than 10.6? The error message being displayed is that the share is unavailable or not on. I was able to confirm all was OK from my wife's MacBook which was still running 10.7. It was able to mount them just fine.

For not seeing how to delete a post, I thought I'd note that this is no longer an issue. Restarting seems to have corrected the problem. Not sure what the problem was originally, but all appears to be OK now.

Similar Messages

  • Systemd failing to mount a network share

    I just installed systemd and I'm having some problems getting it to reliably mount the network shares I have listed in /etc/fstab.  In case it is relevant, I should note that I have opted to install systemd alongside the usual initscripts.  I've created two different Grub menu entries to select between the two systems during boot.
    The relevant fstab entries are as follows:
    //192.168.1.54/MP3z /mnt/MP3z/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
    //192.168.1.100/share /mnt/share/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
    //192.168.1.100/docs /mnt/docs/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
    This is what I've observed with respect to mount failures:
    The share at 192.168.1.54 mounts every time without fail.
    Usually, one of the other two shares at 192.168.1.100 will fail to mount while the second share at the same ip address will succeed.  Which of the two that fails is apparently random.
    Only very occasionally will both shares at 192.168.1.100 mount successfully.
    So far, I have never seen both of these shares fail to mount on the same test run.
    I have tried changing the order of the fstab entries but it doesn't seem to affect things.
    I've tried adding the "noauto" and "x-systemd.automount" options to my fstab entries.  This seems to make things work although with this setup I think the shares are mounted the first time they are browsed, not during starup.  With these mount options set, the system hangs on shutdown with either the messsage "Unset automount mnt-share.automount" or "Unset automout mnt-docs.automount".
    I thought perhaps that this is happening because my network connection isn't being started in time to mount the shares correctly.  Though, I thought systemd handled these sorts of dependencies without any explicit configuration required.  Perhaps this has something to do with the two shares being on the same host (192.168.1.100)?  I don't have any problems with the third share at 192.168.1.54.
    Can anyone shed some light?
    Last edited by battlepanic (2012-08-15 19:28:05)

    I had the same problem. While logged in as root, I can't use an alias or Cmd+K to connect to a server, but it works fine as any other user. I tried the link above and after reading the mount_afp man page, it describes two steps needed to mount a server. Here's what I had to put in Terminal to mount a share called Installers:
    The root account does not seem to be getting past the first step when using Cmd+K or an alias to a network share, although this worked in previous versions of OSX.
    This problem was not fixed in 10.7.1

  • A volume failed to mount/Operation cannot be completed

    We bought a MacBook on the weekend. Our Apple concierge insisted that we can keep our music, videos and photos on our Windows XP desktop and "share" the files on the Mac--in other words, we can pull down what we need to edit or save on the Mac as need be.
    We've set up the shared directories on the Windows machine, renamed the Workgroup to match the Mac and disabled the firewall. We've "connected to server" using Finder and can see the two shared directories we've set up.
    But when I click on either one of them, I get an error message: "A volume failed to mount. The volume "Mac" could not be mounted."
    After some time of being on the network, I see a Shared directory in Finder with my PC. If I click on the icon, the title bar says: "Connected as: Guest". The window displays the same two directories as above but when I click on one or the other I get an error message: "The operation cannot be completed because the original item for "Mac" cannot be found."
    I've called Apple technical support and the agent's response was: I don't think you can do that. Just copy your files to the Mac using DVDs.
    Any ideas? We don't want to have to transfer a lifetime of photos, video and music to our laptop--we want to use the XP desktop as our hub.

    I'm having the same trouble. From an Intel Mac Mini running 10.5.3 I've been able to access smb shares fine on an old PC running XP pro. These are shared volumes on external drives on the PC. I can still access them fine from an old PowerBook G4 running 10.5.3, but while I can see computers on the network, if I try to connect to a share on the computer I get the message "the operation cannot be completed because the original item for <share name> cannot be found". If I try to mount it via a shortcut, I get the message "A volume failed to mount. The volume <share name> could not be mounted.
    In the console, I'm seeing things like:
    6/2/08 10:45:01 PM com.apple.coreservicesd[58] NOTE: Using non-mach-based version of client -> server communication, via direct function calls.
    but I don't know if that has anything to do with this or not.
    Has anyone heard of a fix for this?
    Thanks,
    Mark

  • Cannot mount multiple CIFS shares in /home

    I have 2 users, Joe and Fred, who each have their own directory in /home.  I also have a Netapp filer with a CIFS share called CorpData, which has subdirectories for Joe and Fred.
    On the Arch Linux box, I have this for my fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda1
    UUID=d93def89-7611-43c8-a74f-e20bee64bd7e / ext4 rw,relatime 0 1
    //10.1.1.141/CorpData/joe /home/joe cifs credentials=/etc/credentials,noserverino,_netdev,uid=joe,gid=users 0 0
    //10.1.1.141/CorpData/fred /home/fred cifs credentials=/etc/credentials,noserverino,_netdev,uid=fred,gid=users 0 0
    The problem is that at boot time, Joe's directory will be mounted, but Fred's will not.  The reverse is true if I reverse the two entries in fstab.
    If I issue the "mount -a" command after logging in, the second mount does get mounted, but also generates this error message:
    mount error(16): Device or resource busy
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    I did refer to man mount, but since only the second mount is failing, I don't know what I could try differently.  There are many more directories in CorpData, so I don't want to just mount that entire share on /home.

    Looking into this further, it seems that the server is not able to accept the second request so quickly after the first.  Is there any way to insert a delay or sleep command between the two mount entries in fstab?

  • [SOLVED] netfs fails to mount samba mountpoint in fstab

    Answer:  netfs fails to mount my samba mountpoint because eventhough
    network is before netfs, and network is not started in the background, it
    still seems to take a while to complete, but it doesn't block netfs from running.
    If I put some stalling code in /etc/rc.d/network, and make it wait, then netfs
    will mount the shares, because network was allowed to start and netfs can
    it can find the servers.
    Now, what I want to know is why my network starts up so slowly.
    ----------------------- Read thread for details ----------------------
    This similar setup is working on my old Gentoo setup.
    fstab
    //tib/public /mnt/network/tib smbfs rw,user,auto,guest 0 0
    tib resolves to a server on my LAN.
    When I boot my ARCH system, it gets to netfs daemon, and times out trying to
    access the server.  I get the message
    5711: Connection to tib failed
    SMB connection failed
    The boot completes, and I log in and get the following
    $ ping tib
    PING tiburon.mill (192.168.0.36) 56(84) bytes of data.
    64 bytes from tiburon.mill (192.168.0.36): icmp_seq=1 ttl=64 time=0.354 ms
    64 bytes from tiburon.mill (192.168.0.36): icmp_seq=2 ttl=64 time=0.371 ms
    and, I can mount it like this (which reads /etc/fstab)
    $ mount //tib/public
    $ ls /mnt/network/tib/ | wc -l
    11
    It seems like ARCH isn't able to use the network until sometime after this point in the boot.  Here's my rc.conf daemons
    DAEMONS=(syslog-ng network netfs crond sshd alsa)
    I tried putting netfs last, but that made no difference.  I also tried to load netfs in the background without benefit.
    Note:  cifs doesn't work either; and I get more descriptive errors
    :: Mounting Network Filesystems
    mount error: count not find target server. TCP name tib/public not found
    No ip address specified and hostname not found.
    OK, that clear enough.  But, the hostname is found right when the boot process finishes and I get a prompt.
    And, I've tried the ip address, and FQDN too.
    Any ideas?
    Last edited by ristretto (2007-07-24 05:04:57)

    ok, gave it a try.
    //tib/public /mnt/network/tib cifs rw,user,noauto,guest 0 0
    $ cat /etc/rc.d/local
    #!/bin/bash
    mount //tib/public
    $ grep DAE /etc/rc.conf
    # DAEMONS
    DAEMONS=(syslog-ng network netfs crond sshd alsa local)
    Note local at the end.
    Now, all the daemons load up quick, and then local goes and times out, and I
    get the same error.
    mount error: count not find target server. TCP name tib/public not found
    No ip address specified and hostname not found.
    putting mount in .bash_profile is a bit of a security issue (though not really on my setup)
    but, more importantly, it mounts each time I log in to that account (say each ssh window to the box.)
    I'm thinking it's a bug in the initialization process somewhere?  I've never had this problem on other distros.
    What thinks you?

  • Deleted disk image generates warning that disk image failed to mount

    When I got a new MacBook a month ago, I created a disk image to share an iPhoto library on the same computer. Now I am using an external hard drive to share the library. I deleted the disk image in Disk Utility, but when I start up I get the warning that the disk image failed to mount.
    Any ideas?

    Deleting the disk image from the trash seems to have fixed the problem.

  • "Volume Fails To Mount" Error

    I have Leopard 10.5.8 and am trying to connect to a Windows Vista share via SMB. The two systems can communicate and authenticate without issue. After using Finder's Go To Server and connecting via SMB, I am prompted for a username and password. Once given, the Vista machine authenticates and presents me with a list of shared folders to chose from. At this point, when I select a folder, Leopard immediately returns with the "Volume Fails To Mount" error and I am returned to the list of shares after closing the dialog box. Thinking it might be an issue with Finder, I found and downloaded an application, AutomountMaker. Its results were the same. I can connect from the Vista machine to Leopard with no issues whatsoever, so I know the machines are working together. I have been unable to find any explanation for this error message nor how to correct the issue. I would appreciate it if anyone can offer some ideas.
    As a bit of additional information, I have another machine that is running Windows 7 and I was able to connect to a share on its drive from Leopard without a problem.

    This page may help http://www.ifelix.co.uk/tech/3022.html

  • Time Machine failing to mount backup volume

    Hi
    I set up a network shared drive (afp) and successfully used it for Time Machine backup from one of my Macs.
    However, from my other Mac, when I turn on TM and choose the network drive, nothing happens -- in the TM preference pane the disk doesn't get selected and the message remains "Choose Backup Disk...". In the console I get the following:
    20/5/08 4:39:13 PM System Preferences[185] FSMountServerVolumeSync received error: -36
    20/5/08 4:39:13 PM System Preferences[185] Failed to mount url: afp://;AUTH=No%20User%[email protected]/500GB%20Network%20Storage
    Any ideas?
    Thanks!

    Here's the solution:
    During the backup attempt Time Machine creates the bundle image on the share. This is called <computer’s name>_<string>.sparsebundle (by the way, string is the MAC address of the local en0 device without colons). You should keep the exact name in mind (e.g. by copy & paste or by looking in Console or by constructing it yourself from computer’s name and MAC address).
    Afterwards you start Disk Utility and create another “sparse bundle disk image” on your local drive. Volume Size should be the designated maximum size of the Time Machine backup (don’t be afraid, only by using the image it will increase in size). Further parameters: Volume Format - Mac OS Extended (Journaled); Partitions - No partition map.
    After this use the exact name Time Machine assigned to its bundle image to rename your newly created image (if not already done while creating your own image). Finally you copy the image on the share and manually start a backup via menu bar.
    Voilà. Afterwards Time Machine should start the tedious initial backup.
    from http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/

  • Mounting an NFS share

    Hi,
    I'm attempting to mount an NFS share and having no success.  Regardless of the settings I try, the Finder still denies me access to the NFS share, even though it mounts fine.  I seem to have no read or write access to the share.
    I've tried exporting the share (in /etc/exports on the server machine) in two ways: with
    /home/REDACTED/share     REDACTED/28(rw,sync,all_squash)
    And
    /home/REDACTED/share     REDACTED/28(rw,sync,insecure,all_squash,anonuid=1001,anongid=1001)
    In the second example, the anonuid and anongid are those of the shared folder's owner and group.  I added "insecure" because a how-to on the web claims that OS X won't work with any shares that don't have this specified.
    With either of these settings applied, Disk Utility verifies the existence of the share, and mounts it.  However, I can neither read files within, or add files to, the shared folder.  The error produced is:
    The folder “share” can’t be opened because you don’t have permission to see its contents.
    I have tried the following Advanced Mount Parameters, each to no effect:
    nodev resvport nolocks locallocks intr soft wsize=32768 rsize=3276
    nodev nosuid resvport nolocks locallocks intr soft wsize=32768 rsize=3276 ro
    nodev,nosuid,resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
    nodev,nosuid,resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276 ro
    resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
    -i,-s,-w=32768,-r32768
    -P
    I'd rather not employ SAMBA, and the Apple File Sharing package for my server's OS (Ubuntu 11.10) appears to be bugged currently.  Besides, NFS would be a far neater solution.
    Any helpful advice?
    S.

    Scotch_Brawth wrote:
    I've simply come at NFS as being the most appropriate file-sharing implementation for my needs - it supports automatic mounting at boot using tech native to both my Linux OS and OS X. 
    That is part of the problem. NFS is designed for environments where all servers are mounted (by root) at boot time and permissions are managed via NIS or LDAP. That is the default setting. If you are using something else, it requires some hacking.
    I've had SAMBA working in the past, but I guess a certain air of contamination creeps in when using a Windows protocol to allow interaction between two UNIXy systems.
    Plus, you would now have two different 3rd party reverse-engineered reimplementations of a foreign protocol.
    AFP would be great, but despite receiving support on the Ubuntu forums and IRC, I failed to get it to work - it may be bugged; which would not be surprising, as 11.10 (with Kernel 3) has proved problematic in several other ways.
    Perhaps Ubuntu is targeted more towards desktop rather than server usage. About the time I last played with NFS, I also played with Netatalk - with disastrous results. Supposedly Netatalk is better now. It's authors would be more than happy to sell you a support package.
    I did use the default settings - they failed to allow a working NFS share.  I then applied the variety of settings as recommended by apparently knowledgeable people.  Still no success.  I have read that UID/GID settings are an important aspect of NFS, but the issue in this case (as far as I understand it) is that all UID/GIDs below 1000 are privileged in Ubuntu 11.10, whilst on OS X these are below 501.  So, the choice is either to give the shared folder owner a privileged UID/GID pair, or change the UID/GID of my Mac users to meet the NFS servers needs - not something I'm happy to do for so small a gain.
    You can create a throwaway account on the Mac and just reset the GID/UID to values equal to an account on the Linux machine. That would establish that it is properly working in the default configuration. Then you could edit /etc/idmapd.conf.
    For that reason, I use the "all_squash" option, because the share in question is not for anything remotely critical and the data to be transferred and stored is both worthless and transitory.
    Since all_squash maps everything to nobody, you would have to hack up the permissions on the server to make everything world writeable. I think it will work with /etc/idmapd.conf and without all_squash.
    I know nothing about NFS other than that its capabilities and integration meet my needs.
    Just what are your needs? If the data is worthless and not critical then Netatalk might be the best option. If you can't get that to work, you could try MacFUSE on the Mac side and mount over sshfs. That is normally what I do. It isn't all that reliable, but you don't seem to require that.
    What information I did find regarding OS X and NFS was that there were peculiarities that required certain settings to be present on the server and the client respectively - for example, OS X apparently requires "insecure" to be set as an option, or it simply won't connect properly.  I don't know why, but I have no choice to trust to the advice of others in this case, until I have sufficient grasp to take care of the whole thing myself.
    This goes back to the expectation that NFS expects to be always connected and mounted by root. Apple sells very few desktop machines anymore so it assumes a different, user-centered environment. You could use "insecure" on the server side to allow connections from "insecure" ports > 1024 that a regular users can connect with via the Finder. You could use the terminal with "sudo mount_nfs -o resvport" to tell the Mac to use the root user to connect via a secure port instead.
    If you genuinely think you're able to help, then I'm happy to hear your advice.  What would you recommend?
    I appreciate your meeting me halfway. I think all you really need is /etc/idmapd.conf without all_squash. Then you could setup AutoFS and you could use NFS in a modern environment without even bothering to mount it.

  • External USB Maxtor One-Touch 3  suddenly fails to mount on MacBook Pro:

    External USB HD suddenly fails to mount on MacBook Pro:
    My One Touch III 600GB drive, external power supply, suddenly will not mount and is not recognized by the system profiler or Disk Utility, however, drive, connected USB, appears under windows XP.
    1. Power cable and usb cable working.
    2. Using external AC adapter(not relying on USB power).
    3. Other USB devices, mice, flash drives work on both USB ports.
    4. Drive works on Windows, folders and data integrity ok.
    5. Drive format is NTFS.
    6. No Maxtor software installed.
    7. No humming or strange noises emanating from drive.
    8. No problem to January 14, 2008,
    9. Mac OS 10.4.10 updates last downloaded and installed Jan 20, 2008.
    10.1 blip of the light on "The One Touch Button", then light turns solid white.
    Questions:
    1. Does Apple set sleep or lock switch for devices (drives)?
    2. If so, can it be reset manually?
    3. Does Apple have configuration profile for devices, like a registry key?
    4. If so, where is it located?
    Configuration:
    Dual 2 GHz MacBook Pro 15”
    2 GB DDR SDRAM
    OSX 10.4.10
    2 USB Ports Left and Right

    NOTE: This Update is required when using a OneTouch Drive as a bootable device. Seagate suggests that you dismount and disconnect your FireWire Drive before continuing.
    Users have identified issues when connecting OneTouch External Drives to FireWire Ports on their Mac G4 and/or G5 computers. These Problems range from system hangs, kernel panics to slow data transfer rates. The cause of these problems has been traced back to the FireWire Driver. Seagate has resolved these problems through updated FireWire Drivers.
    I am using USB and not trying to use drive as a boot device.

  • How to allow users to mount a Samba shares on a WXP

    Through lots of reading I've managed to get an understanding of how to mount SMB shares at bootup by placing the proper edits in /etc/fstab. While having the shares of the server, running Contribs.org SME Server 6.01 (recently known as Mitel SME Server) and acting as a samba server, being mounted at startup is perfect since the server is always on. This is not the best idea for the XP workstation since it isn't always on. Here is a copy of my present fstab file with x's replacing the passwords.
    fstab               [B---]  0 L:[  1+19  20/ 21] *(1085/1086b)= .  10 0x0A
    # /etc/fstab: static file system information
    # <file system>        <dir>         <type>    <options>          <dump> <pass>
    none                   /proc         proc      defaults            0      0
    none                   /dev/pts      devpts    defaults            0      0
    none                   /dev/shm      tmpfs     defaults            0      0
    tmpfs                  /tmp          tmpfs     defaults            0      0
    sysfs                  /sys          sysfs     defaults            0      0
    usbdevfs               /proc/bus/usb usbdevfs  defaults            0      0
    /dev/cdroms/cdrom0     /mnt/cd   iso9660   ro,user,noauto,unhide   0      0
    /dev/cdroms/cdrom0     /mnt/dvd  udf       ro,user,noauto,unhide   0      0
    /dev/floppy/0          /mnt/fl   vfat      user,noauto,unhide      0      0
    //192.168.2.2/stuff    /mnt/silicon2 smbfs username=kingnubian,password=xxxxxxx,user
    //192.168.2.105/e-smith   /mnt/silicon1 smbfs username=kingnubian,password=xxxxxxx,users,noauto
    /dev/discs/disc0/part5 swap swap defaults 0 0
    /dev/discs/disc0/part1 / xfs defaults 0 1
    I would like users with an account on the Linux box to mount the remote share on the XP box without needing to SU and consequently need the root password. When trying now to mount "e-smith" (The share on the XP box) as a user using "mount /mnt/silicon1" I get a message about needing to be SU.

    To allow users to mount smb shares you need to make smbmnt suid:
    # chmod +s /usr/bin/smbmnt
    Note however that the user needs to own the directory used as mountpoint. So I don't know how to make 'mount /mnt/silicon1' in your setup work for all users.
    For the users to be able to unmount the smb shares as well you need:
    # chmod +s /usr/bin/smbumount
    Now users can do 'smbmount //server/share mountpoint -o username=whatever' or simply 'mount mountpoint' if the details are specified in fstab. To unmount root can do 'umount mountpoint' or users can do 'smbumount mountpoint'.
    Don't confuse smbmount with smbmnt - the first is the command you use to mount shares manually, the second is the one that should be suid and is used both by smbmount and by mount -t smb.
    Hope this helps.
    -bogomipz

  • How can a mount a NFS share exported from OpenBSD?

    Hello Apple Discussions:
    I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
    Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
    However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
    I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
    After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
    http://www.bsdforums.org/forums/showthread.php?t=54308
    Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
    I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
    But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
    Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
    ON THE OPENBSD BOX:
    #/etc/exports
    /fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
    /exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
    #/etc/hosts.deny
    ALL: ALL
    #/etc/hosts.allow
    ALL: 192.168.222.233 192.168.222.253
    #/etc/rc.conf.local
    portmap=YES
    lockd=YES
    nfs_server=YES
    #here's proof that the daemons are running on the OpenBSD box;
    rpcinfo -p localhost
    program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100005 1 udp 863 mountd
    100005 3 udp 863 mountd
    100005 1 tcp 613 mountd
    100005 3 tcp 613 mountd
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100003 2 tcp 2049 nfs
    100003 3 tcp 2049 nfs
    100021 1 udp 895 nlockmgr
    100021 3 udp 895 nlockmgr
    100021 1 tcp 706 nlockmgr
    100021 3 tcp 706 nlockmgr
    # actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
    ON THE TIGER SERVER:
    # here's proof that tiger server sees the mounts:
    showmount -e 192.168.222.111
    Exports list on 192.168.222.111:
    /fives 192.168.222.0
    /exports/fives 192.168.222.233 192.168.222.253
    # here's the result of user fives' attempt at mounting a share:
    sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
    mount_nfs: /imports/fives: Permission denied
    # yet user fives has no problem mounting same share on linuxppc box.
    What is different about OSX server? I thought it was supposed to speak NFS?
    ---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

    One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
    Each user is free to choose which of those tracks they want in their library.
    There is an Apple help article on multiple users.
    http://docs.info.apple.com/article.html?artnum=300432

  • How Do I find out what app is auto-mounting a network share and stop it?

    I have a new laptop, the 13" rMBP.  I installed Steam and wanted to use the network share on my server to store the game files.  Everything went OK.  I closed Steam, disconnected the share and shutdown my laptop.  When I opened my laptop later on at work, it started to try and mount the network share.It keeps on going it.  I removed the Steam app and all files related to Steam that I could find.  I've looked at fstab, auto_home, auto_master and a large list of other files and directories and I *still* cannot find the offending file that's auto-mounting the share.  It's really frustrating.
    The share auto-mounts when I am home but not on the desktop or in finder.  I find it by looking at /Volumes/ in terminal.  If I mount the share manually under /Volumes/ it shows as Games-1 and mounts on the desktop under Games.
    Does anyone have any ideas on where I should be looking to find the offending process/file/daemon?
    Thank you!
    Trevor

    thanks for the reply but are you sure about this? What difference would it make? Why 5 apps?
    Even if it does work, which I doubt, at some point, I will have to resync ALL my apps again and surely the same thing will happen again, and I will be none the wiser. I still won't know which app it is. There must be a way of finding this out.
    Any ideas?
    What is really freaking me out is how it is connecting to my carrier (who is charging me) with Cellular data switched off.......?
    Thanks again.

  • All downloads failing to mount and iTunes not recognising iPod!

    My iBook G4 (Model No A 1055) needs alot of updates however i can't install anything. It downloads to the Desktop fine but when i go to open the attachment so i can actually install it a message comes up saing "The following disk images failed to mount" and the reason is a "corrupt image". I have tried to do this with Firefox, iTunes and Adobe and they all say the same!
    I also now have issues with iTunes (7.2) which is all of a sudden not recognising my iPod shuffle (2nd gen). It doesn't come up in devices or anything when plugged in my iPod shuffle will just flash orange a few times and then nothing. I have tried to connect it to another (and much newer) Mac computer however it doesn't recognise it on there either.
    Has technology just got so good my lappy is basically extinct and i need a new one or is there something i / Apple can do to help get me up to date with everything? Any help and feedback would be really appreciated.
    Thanks
    Louise

    if you are running OS 10.3, it's pretty much obsolete
    you can try getting OS 10.5 installed, but it can slow down the computer, 10.4 is not much use anymore either.

  • Unable to mount a network share drive in mac os 10.7 when logged in as root

    I enabled the root account by entering sudo passwd root in the terminal window. Once the account was enabled successfully, I logged out from my admin account and logged in as root. I then attempted to mount a network share running on an Xserve and a Windows share but was unable to. I logged out as root and logged back in using my admin account and I was then able to mount both shares successfully.
    Is there a new Lion security feature that prevents the root account from mounting network shares? If so how can I get around it?
    Thanks for your help.

    I had the same problem. While logged in as root, I can't use an alias or Cmd+K to connect to a server, but it works fine as any other user. I tried the link above and after reading the mount_afp man page, it describes two steps needed to mount a server. Here's what I had to put in Terminal to mount a share called Installers:
    The root account does not seem to be getting past the first step when using Cmd+K or an alias to a network share, although this worked in previous versions of OSX.
    This problem was not fixed in 10.7.1

Maybe you are looking for