Autofs doesn't automount nfs4 shares

I'm trying to automount NFS shares using autofs. All in all, NFS is configured correctly, as I can manually mount the share on the command line.
user@client:~$ sudo mount -t nfs4 myserver:/home /mnt
user@client:~$ mount | grep myserver
myserver:/home on /mnt type nfs4 (rw,addr=192.168.9.20,clientaddr=192.168.9.8)
user@client:~$ df | grep myserver
myserver:/home 480719104 421950976 34348800 93% /mnt
user@client:~$ sudo umount /mnt
user@client:~$
Following the instructions on the wiki, I install the autofs package, I add the required line in /etc/nsswitch.conf, and modprobe nfs4. Here is my /etc/autofs/auto.master file :
# Sample auto.master file
# Format of this file:
# mountpoint map options
# For details of the format look at autofs(5).
#/media /etc/autofs/auto.media
/net -hosts --timeout=60
Finally, I start the autofs daemon as such :
user@client:~$ sudo /etc/rc.d/autofs restart
The daemon starts fine, but I can't access the NFS shares as I should :
user@client:~$ cd /net
user@client:/net$ ls -l
total 0
dr-xr-xr-x 2 root root 0 Aug 6 22:40 localhost.localdomain
dr-xr-xr-x 2 root root 0 Aug 6 22:40 myserver
user@client:/net$ cd myserver
bash: cd: myserver: No such file or directory
user@client:/net$
What have I done wrong? What more must I do to use my NFS shares with autofs?
Thanks.

good luck.
I'm having this problem since autofs5 came out. (which is a few years now), and no one knows the solution.
see https://bbs.archlinux.org/viewtopic.php?id=79513

Similar Messages

[SOLVED] Can't get autofs to work with NFS4

NFS share mounts successfully either from fstab or manual mount, but autofs doesn't seem to be able to handle it.
My /etc/autofs/auto.master:
/nfs /etc/autofs/auto.nfs
/etc/autofs/auto.nfs:
mountpoint -fstype=nfs4 serv1:/mnt/stor
And then:
# systemctl reload autofs
$ cd /nfs/mountpoint/
bash: cd: /nfs/mountpoint/: No such file or directory
Am I doing something wrong with autofs?
Last edited by nesk (2014-09-15 06:23:44)

Here they are:
# automount -d -f -v
Starting automounter version 5.1.0, master map auto.master
using kernel protocol version 5.02
lookup_nss_read_master: reading master files auto.master
parse_init: parse(sun): init gathered global options: (null)
lookup_read_master: lookup(file): read entry /nfs
master_do_mount: mounting /nfs
automount_path_to_fifo: fifo name /run/autofs.fifo-nfs
lookup_nss_read_map: reading map file /etc/autofs/auto.nfs
parse_init: parse(sun): init gathered global options: (null)
mounted indirect on /nfs with timeout 300, freq 75 seconds
st_ready: st_ready(): state = 0 path /nfs
handle_packet: type = 3
handle_packet_missing_indirect: token 565, name mountpoint, request pid 2124
attempting to mount entry /nfs/mountpoint
lookup_mount: lookup(program): looking up mountpoint
lookup(program): lookup for mountpoint failed
dev_ioctl_send_fail: token = 565
failed to mount /nfs/mountpoint
handle_packet: type = 3
handle_packet_missing_indirect: token 566, name mountpoint, request pid 2124
dev_ioctl_send_fail: token = 566
handle_packet: type = 3
handle_packet_missing_indirect: token 567, name mountpoint, request pid 2124
dev_ioctl_send_fail: token = 567
Those last 3 lines appear every time I try to cd into /nfs/mountpoint/

My iphoto doesn't allow to share the photos to facebook anymore. (publish button doesn't work) does anyone knows what is wrong?

my iphoto doesn't allow to share the photos '09 (8.1.2) to facebook anymore. publish button doesn' work. (it used to be OK) anyone has any idea?

There are a couple of things that could be causing this. Try:
delete your iPhoto cache
hold down the option key
in the Go menu in the Finder, scroll down to Library
in Library, find Containers/com.apple.iPhoto/Data/Library/Caches/com.apple.iPhotoin that folder, find Cache.db and drag it to the trash.
delete the iPhoto preference file
do the same trick with the option key to show ~/Library
in Library/Preferences, find com.apple.iPhoto.plist, and drag it to the trash
if there are multiples of any of these files, drag them to the trash too.
delete the Keychain entries and do Keychain First Aid
in Applications > Utilities > Keychain Access
in the column on the left select login and under category, Passwords
delete all of the entries that include iPhoto or Facebook
in the Keychain Access menu, scroll down to Keychain First Aid, enter your user password, select repair, and click start.
Then restart your computer
new caches and preference files will be generated
you will need to reenter your iPhoto preferences
reenter your facebook user name and password in iPhoto
this should fix it.
Message was edited by: arthur

NFS4 shares and mounted subdirectories

Hello,
i have some troubles configuring my nfs4 shares on my server. I have some nested filesystem setup, which i should explain first. The directories on my system partition are as follows: (Both directories named "Data" are empty)
/mnt
/mnt/Data
/srv
/srv/nfs4
/srv/nfs4/Data
I mount a LVM volume on /mnt/Data, thats where i have most stuff. On this volume there exists an empty directory "SquashFS", which will then be "filled" by mounting "SquashFS.sqsh" there. Now i can access any stuff unter /mnt/Data on the server.
/mnt
/mnt/Data
/mnt/Data/some
/mnt/Data/things
/mnt/Data/SquashFS.sqsh
/mnt/Data/SquashFS
/mnt/Data/SquashFS/compressed_things...
/srv
/srv/nfs4
/srv/nfs4/Data
Now i want to access all that stuff from my desktop or any other remote computer. Because symlinks are not working here for nfs4, i bind mount /mnt/Data to /srv/nfs4/Data and export the directory with the "nohide" option. I can access all stuff, but /srv/nfs4/Data/SquashFS is empty.
So i tried to bind mount /mnt/Data/SquashFS to /srv/nfs4/Data/SquashFS, but that didn't helped. Next i could try out to export /srv/nfs4/Data/SquashFS with the "nohide" option. I think that this will work, but i have the feeling i make something really wrong. With a couple of such situations your exports and fstab get mixed up soon, i think.
Somebody have some recommendations or guides how to solve this? Or some tips how to better organize such files?
Thanks in advance,
Fabian

Hello,
The TechNet Sandbox forum is designed for users to try out the new forums functionality. Please be respectful of others, and do not expect replies to questions asked here.
As it's off-topic here, I am moving the question to the
Where is the forum for... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Two quirks mounting nfs4 shares

I've just spent some time troubleshooting a nfs4 setup that used to work fine but at some recent update broke. I didn't see any discussion of the issues here, so I thought I'd post what I've learned.
1. Suppose your root exported nfs directory is /srv/nfs, and that you also want clients to be able to access /srv/nfs/subdirectory, which is a directory elsewhere on your drive remounted underneath /srv/nfs. There are two ways to specify this in your /etc/exports file. First, you can add the "crossmnt" option to the line exporting /srv/nfs. (And if you do that, you don't even need a line exporting /srv/nfs/subdirectory, if the clients are never going to ask to mount it directly.) Alternatively, you can add a line exporting /srv/nfs/subdirectory, and specify the "nohide" option on that line.
I used to use the "crossmnt" option, but it turns out that with recent nfs4 updates this has broken. I found some discussion of the issue here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567546, which says that upstream is aware of the problem but it's not clear when a fix will arrive. That report said that the issue affected nfs-utils 1.2.1 and 1.2.2, and that the problem appeared with both the "crossmnt" and "nohide" options. Perhaps it did once; I can report though that now the "nohide" option seems to be working, but "crossmnt" still doesn't work.
2. A separate issue has to do with auto-mounting nfs volumes on a client. Suppose your /etc/fstab line has an entry like this:
my_nfs_server:/ /mnt/my_nfs_mountpoint nfs4 noauto,nosuid,nodev,noatime,_netdev 0 0
If the network is available on the client, and the nfs server is active, then formerly one could rely on "sudo mount -a" (or sudo /etc/rc.d/netfs start) on the client mounting the nfs share for you. However this doesn't seem to work anymore. I don't know when it broke.
Note that if there's such a line in your fstab, then just doing:
sudo mount /mnt/my_nfs_mountpoint
will work. You don't need to do a fully explicit, name-the-server-and-netfilesystem-type mount. But for some reason the "mount -a" type commands aren't working.
This recent thread https://bbs.archlinux.org/viewtopic.php?id=102407 about autofs could be connected, though that issue is there said to have been around for a while.
If any readers have insights/further links about these issues, they'd be welcome. As I said, I thought I'd post just to help anyone else who encountered these problems.

• . . . . . .. . . . . . . . . . . ,.-'". . . . . . . . . .``~.,
. . . . . . . . ./. . . . . . . . . . . . . . . . . . . . . . . . . . ,:`^`.}
. . . . . . .?. . . __. . . . . . . . . . . . . . . . . . . . :`. . . ./
. . . . . . . /__.(. . ."~-,_. . . . . . . . . . . . . . ,:`. . . .. ./
. . . . . . /(_. . "~,_. . . .."~,_. . . . . . . . . .,:`. . . . _/
. . . .. .{.._$;_. . ."=,_. . . ."-,_. . . ,.-~-,}, .~"; /. .. .}
. . .. . .((. . .*~_. . . ."=-._. . .";,,./`. . /" . . . ./. .. ../
. . . .. . .\`~,. . .."~.,. . . . . . . . . ..`. . .}. . . . . . ../
. . . . . .(. ..`=-,,. . . .`. . . . . . . . . . . ..(. . . ;_,,-"
. . . . . ../.`~,. . ..`-.. . . . . . . . . . . . . . ..\. . /\
. . . . . . \`~.*-,. . . . . . . . . . . . . . . . . ..|,./.....\,__
,,_. . . . . }.>-._\. . . . . . . . . . . . . . . . . .|. . . . . . ..`=~-,
. .. `=~-,_\_. . . `\,. . . . . . . . . . . . . . . . .\
. . . . . . . . . .`=~-,,.\,. . . . . . . . . . . . . . . .\
. . . . . . . . . . . . . . . . `:,, . . . . . . . . . . . . . `\. . . . . . ..__
. . . . . . . . . . . . . . . . . . .`=-,. . . . . . . . . .,%`>--

Creation of undesired Automount of Shares in 10.9

I'm experiencing one problem that is made worse by another problem. This appears to be a new bug under 10.9 and while I will report it to Apple I'm trying to work around it for now but my inability to find where Apple stores the automount info now in 10.9 is making it impossible. Here is what is happening under 10.9:
If a network sharepoint is mounted on a 10.9 client and the server which is hosting that sharepoint restarts or otherwise goes offline for a short period the client machine will apparently create an automount entry for that sharepoint if you do not choose the "Disconnect" option when the OS informs you the server is gone. By doing this when the server comes back up it will be mounted automatically. This actually is a very nice feature, however when it runs into this other bug:
HOW TO Mount a Network Share using the Automount as non-root
it becomes a nightmare. Briefly this bug is that anything mounted via autofs mounts as ROOT (and not as the logged in user, which is what occurs when you use command-K Connect to Server), therefore even though it is mounted the user cannot access it at all. If you look at the /Volumes folder you can see the share is there but there is no disclosure triangle (meaning you can't see the contents) and clicking on it only confirms that by giving you the "you don't have permission" message.
The real problem now comes in when you restart. When you restart the client the machine mounts that share prior to the Finder loading.... and even if you have an actual alias to the share as well in startup items, it simply points to that already mounted root-owned share you have no access to, so you get an open window that is empty. Also any reference to that sharepoint in the dock is empty. You can then do Connect to Server and manually mount it again, and it does give you access, but it mounts as SHAREPOINT-1, so the reference in the dock still does not work thus removing any utility by having a reference to it in the Dock. So there is no way to have these shares that the OS helpfully tried to make automount actually mount automatically at login or restart! Oh the irony. The only work around is to just not do that and to manually unmount them from /Volumes and then to remount them using command-K (aliases only seem to point to SHAREPOINT not SHAREPOINT-1).
So my question at this point is this: Where the heck is Apple storing these autofs entries telling it to mount these shares automatically. I've seen references online to /etc/autofs but I don't have that file in my /etc folder and although I do have auto_home, auto_master, autofs.conf none of those contain anything with any sort of reference to the shares in question I'm having a problem with. I'm thinking if I can just find the correct file I can simply remove those references (or delete the file if it is a cache) to restore normal behavior of not automounting.
Or Apple could fix the bug that mounts these things as ROOT instead of as the logged in user. But it seems it has been around for at least 3 years so I'm not gonna hold my breath.
As an addendum, this occurs whether or not the server that got disconnected is OS X Server. I have an OS X Server 10.8 and a regular 10.9 both sharing up folders and this occurred on a client for both. It is strictly a client side issue.

Problem resolved, turned out to be an application, Synk Pro, that was mounting these servers as root so it could do its syncing if they ever became unmounted.

Autofs won't automount

Hello everyone,
I followed the wiki for autofs step by step (minus the things I don't care about, I only need usb and cd/dvds to automount) and when I was done I still couldn't get it to actually automounting.
What could I do to see where the error is?

*************EDIT: SOLVED**************
I had probably forgotten '1' at the end of sdb1, now my /etc/autofs/auto.misc looks like this:
flashb -fstype=auto,async,nodev,nosuid,umask=000,gid=disk :/dev/sdb1
I also removed --timeout option in auto.master, and autofs is working fine now.
I have exact same problem.
More info:
1. Flash drive has a 1gb ext4 partition and works perfectly elsewhere.
$ lsblk /dev/sdb
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 1 954M 0 disk
└─sdb1 8:17 1 953M 0 part
$ sudo fdisk -l
Disk /dev/sdb: 1000 MB, 1000341504 bytes, 1953792 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00056ce1
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953791 975872 83 Linux
2. Modprobe'd autofs4, but doesn't show up in lsmod, is this normal?
$ modprobe autofs4 && lsmod | grep autofs4
3. Autofs config files:
/etc/autofs/auto.master
# Sample auto.master file
# Format of this file:
# mountpoint map options
# For details of the format look at autofs(5).
/media/autofs /etc/autofs/auto.misc --timeout=1
/etc/autofs/auto.misc
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
usbstick -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sdb
cdrom -fstype=iso9660,ro,nodev,nosuid :/dev/cdrom
#floppy -fstype=auto,async,nodev,nosuid,umask=000 :/dev/fl
/etc/conf.d/autofs
#localoptions='rsize=8192,wsize=8192'
# e.g. --timeout=60
daemonoptions=''
There is this line in /etc/nsswitch.conf
automount: files
4. Daemon looks ok
$ sudo systemctl status autofs
autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)
Active: active (running) since Sun 2013-04-14 14:42:54 AMT; 28min ago
Process: 2405 ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid (code=exited, status=0/SUCCESS)
Main PID: 2407 (automount)
CGroup: name=systemd:/system/autofs.service
└─2407 /usr/sbin/automount --pid-file /run/autofs.pid
Apr 14 14:42:54 work2 systemd[1]: Started Automounts filesystems on demand.
5. Permissions of /etc/autofs/auto.master /etc/autofs/auto.media /etc/autofs/auto.misc /etc/conf.d/autofs are all 644 ( -rw-r--r-- ).
Any help appreciated.
Last edited by axper (2013-04-24 18:56:18)

Automounting AFP shares... no seriously

I simply cannot get my head around the file sharing capabilities of Leopard/Snow Leopard. Sure it has NFS support, but from time to time it dies and one have to reboot in order to remount. So I (try to) switch to native AFP. Again I cannot mount manually using mount_afp nor can I mount using auto_master file syntax.
I have checked several tutorials and they do it exactly the same way I do it. I can mount my shares from "Connect to server..." no problemo, but automounting is never working.
I just can't understand why Apple has made it so difficult to get a basic file sharing up and running AND to make it automatic. Why on earth it this so problematic all the time. Ridiculous.
If anyone at all has SL running with automatic AFP shares mounted on boot (not using Login items, I don't want them in my face every time I boot) please tell me your syntax. And Apple, come on... why make it so difficult?

I agree that the lack of documentation and of GUI options to do this is quite puzzling and frustrating.
I guess they want you do it using login items.
I'm not an expert on the issue (I wish somebody who IS one would pop in) but I sort of managed to do it using /etc/fstab as described here
http://blogs.sun.com/lowbit/entry/easyafp_autmount_onos
It works but I'm not sure if did it completely correctly because I have to drill in quite deep before i get to the actual share when I start on "All" in the sidebar. also, the mounted share does not show up on the desktop even when I have the option to do so checked in finder preferences.

Bug/incompatibility? SnowLeopard server problem automounting group share point on Lion clients

I've been using Wazza's Server Notes for Snow Leopard server, with great success. But now I've run into something that I don't think is user error.
Here's the rundown: school network, mix of PPC Leopard, Intel Snow Leopard, and Lion clients running off a Snow Leopard server. Clients are bound with server. Things that work great: account access, managed preferences, file sharing, mobile accounts, even network image deployment.
Now the latest obstacle: only on Lion clients, the Group Sharepoint will not automount. I know it's not mounting (as opposed to merely not being seen). Finder is configured correctly. I know it's not a conflict of managed preferences--I isolated this one managed preference from the others to make sure of that. And moreover, the Group Sharepoint appears fine, using any user account on any Snow Leopard client. Only the Lion clients don't cooperate.
I have heard rumors that Lion is still a little bit buggy. Is that the culprit? Or is it rather that Apple wants me to upgrade my server to Lion if I have Lion clients?
Regardless, is there a workaround?
Thanks for any input. The help and education I get here is amazing,

Well, no, now I've eliminated that line of reasoning. I had no problem getting the User Home Sharepoint automounted, via computer-group managed preference. Which means that in principle there shouldn't be problems automounting in a lion client.
What I am noticing is that, in general, the lion client is having plenty of success handling managed preferences of computer groups in WGM, but not User groups. For example, the lion client stops loading one of my startup apps if I use user-group preferences to set it.
Problem is, the group Sharepoint can only be ticked on within the users and user groups preferences. Too bad it doesn't do anything,

Pages (latest ed) doesn't let me share documents through email anymore.

I updated to the the Mavericks when it was released and updated my copy of Pages along with it. Pages was working flawlessly until yesterday when it was having trouble connecting to my Mail (and hence my Gmail) account. This happened even though I checked the connection and the connection seemed perfectly normal. Earlier today when I went to share a doc through the "Send a Copy" tab and when I scrolled over this I was given two options. Share document through Messages or through AirDrop. The email option had completely vanished! I checked my Mail account's connection to Gmail and everything appeared normal. I disconnected the account and reconnected it to be safe and tried again. Still no "Mail" option. I then deleted my copy of Pages 2013, restarted my comp and redowloaded it. Still no "Mail' option! (I also scanned Pages with 2 different virus detection apps {VirusBarrier Express & ClamXav} and both didn't find a thing wrong with it. Also I ran DiskUtility & that also found nothing wrong.)

PieMatey wrote:
Earlier today when I went to share a doc through the "Send a Copy" tab and when I scrolled over this I was given two options. Share document through Messages or through AirDrop. The email option had completely vanished!
See About the new iWork for Mac: Features and compatibility. That is not one of the features they plan to restore in the next six months.
Send feedback. There are forms for Keynote and Numbers, as well.

External drive doesn't automount using HAL

Hello everyone, this is a problem I've been struggling with for about a week now, still no solution!
Bascially I want HAL to automount my external HD (USB) at start up as it has my music etc etc. I usually boot with the drive in the USB slot. Sometimes the drive is visible and I just need to click on it to mount it, others I need to unplug and plug it back it and it's fine, but I can't just boot up and have it available. I'm using KDEmod and have unchecked the "Mount as user" box as suggested by a forum I read, made no difference.
Under "ownership" both the user and group of the drive are "root", but this is the same with all my mounted drives, including my /home. My DAEMONs list from /etc/rc.conf is below
DAEMONS=(syslog-ng @ipw3945d !network !net-profiles hal dhcdbd @networkmanager !netfs !crond @alsa @fam @kdm laptop-mode)
I have nothing to do with HAL in my MODULES line, should I? Thanks in advance! Let me know if ya'll need more information
*edit* everytime I have booted recently the drive is visible under "Storage" but unmounted.
Last edited by rettie (2008-08-25 22:30:45)

I have since got this working using the uDev solution at the bottom of this page:
http://wiki.archlinux.org/index.php/Udev
yay now just need to sort the folder permissions on it (sigh)
*starts new thread...*

Why my Routeur Netgear DG834G doesn't allow to share my ITunes library ?

My config : a modem-routeur Netgear DG834Gv3
a macpro plugged by ethernet port
a macmini by wifi
a macbook pro by wifi
Since I 've installed this routeur, internet access and sharing works well but I can't see my shared iTunes libraries on the different mac at home.
I've tried to create a rule and open a service on the port 3689 in the routeur but it doesn't work. the macos X firewall isn't activated...
Same problem with iphoto libraries
And I dont't see the other macs when I clik on "Server" in the finder window.
Can someone help me ?
Thank you.

Firewall rules usually only apply to the WAN port so unless you have configured the router otherwise, I would close that port.
The one common item to all of your problems is mDNS or Bonjour. That is what Macs use to advertise all of the services you listed. If all devices are on the same subnet, it should work with out any problems unless you have configured the router to filter multicasts.
Are your wired and wireless clients on the same subnet? If they are not on the same subnet, your router would have to route multicasts. Though most "home" routers only route with regard to the WAN port, so I would look for some kind of filter that is stopping multicasts on the local network.
I don't know enough about that router to say what it normally does with multicasts.

Automounting smb share without network daemon

Hello everyone, I have an issue. I'm using networkmanager to manage wireless connections. While installing networkmanger, the wiki told you must remove network daemon from rc.conf, and use networkmanager instead: that's exactly what I did, and networkmanager does the job just well. I told you that because I think that it is the reason why i'm failing to auto mount smb share through editing fstab. If i put in fstab the command described on the wiki (cisf mounting) I get a FAIL at booting, it says it can't find the share. Otherwise am I wrong and the reason must be related to something else, like syntax errors? Thank you.

Trying to follow your advice, I did the following: I put into /etc/fstab
//server/Videos$ /mnt/video cifs noauto,noatime,username=Y3KNET/Arch,password=Ilove69,ip=192.168.1.1 0 0
//server/Public$ /mnt/public cifs noauto,noatime,username=Y3KNET/Arch,password=Ilove69,ip=192.168.1.1 0 0
then, in /etc/rc.local:
mount /mnt/video
mount /mnt/public
and, as a second try,
sudo mount /mnt/video
sudo mount /mnt/public
but without luck: no mount actually takes place. Anyway, if i type the above code after logon into kde, everything works flawlessly. Where am I mistaken?
Last edited by Y3k (2011-12-03 23:06:36)

10.4 Automounting NFS shares at startup - can't stop it!!

Hi,
I am seeing two processes trying to mount a NFS share at startup from a NFS server that nolonger exists - however I cannot find out what is causing these to try to mount - hence I cannot stop them. At the moment I have to kill the two processes for the startup to complete normally. The processes show thus:
dom-forrests-computer:~ marty$ ps -ax | grep nas1
208 ?? S 0:00.00 /sbin/mount -t nfs -o noautomounted -o browse -o suid -o dev nas1:/mnt/array1/mac /Volumes/nas1
209 ?? S 0:00.00 /sbin/mount_nfs -o noautomounted -o browse -o suid -o dev nas1 /mnt/array1/mac
If I look in finders "Connect to server" they are not listed. I cannot see them in netinfo and fstab appears to be a dummy file. Can anyone suggest where I need to look to stop these connecting?
Thx
Dom

Hi Dom_f, and a warm welcome to the forums!
Check System Preferences>Accounts>Login Items window to see if it or something unknown is listed.
Also look in...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
Or try a Safe Boot from the HD, (holding Shift key down at bootup), to see if they still mount.

Itunes doesn't show Home Share words or list of other authorized computers

I have "turned on" Home Share. I have authorized a second computer. When logged in to the second computer, the Itunes screen does not show the option Home Share, or show the names of the authorized computers. So, no sharing of music is possible. What is the fix for this, please? The Help catalog does not answer the question.

I don't know if you've done this already, but you need to:
Turn on "home sharing" turned on all of the relevant computers;
Make sure the computers have to be on the same network;
You just turned on "Home Sharing", some people report that they had to quit iTunes and restart it before "Home Sharing" worked; and
If those previous steps failed to solve the problem, you might want to check the firewall settings on each of the computers to ensure that UDP Port 5353 (which allows the computers to see each other and appear in iTunes on the other computers) and TCP Port 3689 (which allows the actual "Home Sharing" features to work) are both enabled.
See http://support.apple.com/kb/HT1601 for how to configure the default Windows firewall. If you're running a third party firewall (sometimes part of your antivirus software), the particulars of opening the appropriate ports on the firewall may differ.
If you think the problem may be a firewall issue and you're not 100% comfortable with how to "open ports", a quick test would be to temporarily disable the firewall on both machines, restart iTunes on both machines, and see if it works. This is just a test to see if the firewall is the problem, but you should promptly turn your firewall on again and if "Home Sharing" worked while the firewalls were turned off, you just need to proceed with the particulars of opening these two ports on both machines. I've also seen people open the port in their default Windows firewall, but neglect to realize that they might have two firewalls (e.g., neglect to check their antivirus software's firewall). Unfortunately, the particular instructions on how to open the firewall ports will vary from one firewall software package to another. But if you have problems, let us know what firewall software you're running and someone can probably help. (Or just check with your firewall vendor.)
Hope this helps.

Autofs doesn't automount nfs4 shares

Similar Messages

Maybe you are looking for