Apparently this problem can occur for many different reasons. In my case it was solved by re-launching the finder. A description and solution for this was at http://www.cnet.com/news/fix-shared-computer-not-found-in-finder/ .
Digging through the console I found this telling error:
NetAuthSysAgent already_mounted: share <TIMEMACHINE> already mounted
TIMEMACHINE is my share name in this case. As the error suggests, Time Machine is trying to mount the share again which it can't do because it's mounted already. But wait! If I disconnect from the share will leave my list!
A couple of things you need to be aware of.
First - the AFP URL needs to contain the name of the share - not it's location on the server. Second, the mount point must be an empty directory that you have write permission to. So your commands might be :-
sudo mkdir /Volumes/mount
sudo mount -t afp afp://user:pass@ipaddress/SharedDrive /Volumes/mount
Apple Filing Protocol is deprecated1, not "dead". There's a big distinction and that is being deprecated, it's still included and still works at the time of last development but it has been superseded by something else - in this case SMB2. It also means there will be no further development.
Will it stop working in future versions of macOS?
There will ...
In my case (iMac trying to access files on a Win7 machine) the solution was to add permissions for "Guest" to the Win7 directory. This was previously not necessary. The directory was shareable to everybody and it worked. But apparently now the iMac is trying to connect as "Guest" and adding permissions specifically for "Guest" (Properties…Sharing…Share…Add…...
AFP can’t share files on Apple File System (APFS). Apple File System (APFS) is the default file system in macOS High Sierra for Mac computers with all-flash storage. You can't opt out of the transition to APFS when you upgrade a Mac with all-flash storage to macOS High Sierra.
If you need to share files, ...
I would say, rsync away once you are sure the sparsebundles are not being actively mounted or written to by other Mac OS clients.
The beauty of an Apple disk image is that all the Mac unique things are stored internally since they are a filesystem unto themselves and don't rely on your actual storage filesystem in any way. As long as you get the file names ...
Are you sure that all workstations are connected via AFP?
I bet you get the strange folder names because of mangled names = yes (the default) in the samba server configuration. Check Synology bad filenames or Samba name mangling for more information. One solution is to disable SMB on the NAS another is to force OS X to connect via AFP e.g. afp://user@...
Prior to Mac OS X Lion, Mac OS X Client came with SAMBA Server and Client and what you defined to share was all that was shared. Since Mac OS X Lion, and continuing with OS X Mountain Lion and other releases of OS X, SAMBA has been replaced with SAMBX due to SAMBA moving to GPLv3. As a result SAMBA is basically broken in the OS since 10.7. The Mac OS X 10.7 ...
Execute this command: defaults write com.apple.desktopservices DSDontWriteNetworkStores true
Either restart the computer or log out and back in to the user account.
Ok so I am going to answer my own question. In my case the solution turned out to be really 'simple'.
I looked at another Mac and I noticed that the /Volumes directory had different permissions. On the problematic Mac it was set to drwxr-xr-x and on a recently installed Mac it was drwxrwxr-x.
So I fixed my problem with:
sudo chmod 775 /Volumes
(You can ...
Use AppleScript, but do not specify the user name or password.
In my case, none of the suggestions that I found online worked perfectly.
I had several AFP volumes that I wanted to mount automatically. Following the advice given here and elsewhere, the obvious solution seemed to be an AppleScript file with something along these lines:
Setup your NAS to export a NFS-share. Refer to the Synology knowledgebase how to do this or use the following how-to to set it up, fine tune and secure your set-up.
You may do it manually in the command line also:
Let's assume your media folder is /Shares/Media. Create or edit a file named exports in /etc. The example below restricts the access to computers ...
Unfortunately, the source code of the AFP driver is not free software, so it's difficult to give a definitive answer on that. However, it appears that Netatalk supports copyfile, so it's likely that the answer to that question is yes.
If you look at the source code of the latest version of the macOS smbfs driver, you can see that it does implement the ...
You should reconsider a NAS because using a Mac Pro is complete overkill when a NAS will do exactly what you want including sync to public cloud services like DropBox, OneDrive, Box.net, etc.
I am a fan of Synology products because whether you are using their entry level single disk NAS devices or their enterprise grade rack mount solutions, the software ...
It is not possible to access server shares from Apple's iOS. iOS does not have a Samba or AFP client, and thus, cannot handle these requests.
Time Capsule uses modified AirPort Extreme firmware and supports AFP and SMB file-sharing protocols.
Unfortunately, this is the extent of your capabilities of accessing files on Time Capsule from iOS. Sorry :(
It turned out that the issue was indeed different UIDs though the usernames were the same.
From the Apple Support Communities link:
The first user that is established on an OSX disc is given UID number
501. Normally next user is given UID 502. In my case I could not import my existing user during first run with my new MB Air. Had to
It turns out that, as I suspected, a paranoid security configuration was preventing AFP from working.
In particular, the machine had been "hardened" per Apple's security configuration guide in which chapter 9 describes how to disable AFP by unloading the com.apple.afpfs_afpLoad dæmon (I had thought it was only required to serve files, not also to connect to ...
If you are running Windows file shares on Windows Server 2003 R2 and above, you can create file screens that prevent any user from creating any set of pre-specificied files.
I have effectively used this approach to eliminate all mac created files on our file shares.
Please see the MS Technet document, Screening Files, for more information.
While this might not help everyone, if you are running samba on the file server, you can add the following in your smb.conf:
Veto files = /.TemporaryItems/._.TemporaryItems/.DS_Store/
The "Veto files" is a / separated string of filenames (wildcards also allowed) that is forbidden to be created. This resolved the issue for me.
I found this trick on the ...
User access to sharepoints will depend on permissions that are set on that sharepoint. You can use the 'ls' command to get that information using Terminal...Newer Mac products (10.4+) will use ACLs to control access to those folders. You can obtain infomation on both the POSIX as well as ACLs applied to folders by using this command:
ls -ale /Path/To/Folder
I found (what seems to be) a good solution after messing around and observing another AFP share that is working correctly. Turns out that the working folder has ACLs to allow spotlight indexing:
$ ls -led /Shared\ Items/Public/
drwxrwxr-x+ 19 root admin 646 May 6 12:47 /Shared Items/Public/
0: user:_spotlight inherited allow list,search,file_inherit,...
OK, I figured it out. The keys in the auto_afp file are paths that are relative to the path specified in the top-level auto_master file.
So if your /etc/auto_master has: my/global/mount auto_afp
Then your /etc/auto_afp should have: point -fstype=....
Finally to get visibility into what automountd is doing, add AUTOMOUNTD_TRACE=2 to /etc/autofs.conf, ...
Below is a network diagram based on what I have read thus far. I have made some assumptions about the IP numbering conventions, but that will have no effect on the overall scenario.
I am assuming that you are using two different subnets rather than 2 different classes of networks. But, either way, you have two very different network IP addressing schemes ...
Found the solution: The problem was, that the mysqldump command could not be find. I needed to add the absolute path to it /Applications/MySQLWorkbench.app/Contents/MacOS/mysqldump
Thanks to patrix and Allan for that tip.