Hot answers tagged

6

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


4

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


4

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


4

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


4

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


4

I found this script from http://hints.macworld.com/article.php?story=20050215082247458, but I'll reproduce it below. Open up Script Editor and paste in: set sfiles to "afp://user:pass@host/volume" tell application "Finder" mount volume sfiles end tell Replace sfiles with the appropriate details of your AFP volume. Add ...


4

Open Terminal. Execute this command: defaults write com.apple.desktopservices DSDontWriteNetworkStores true Either restart the computer or log out and back in to the user account. Reference: http://support.apple.com/kb/HT1629


4

1. Edit the file /Applications/Tunnelblick.app/Contents/Resources/client.up.osx.sh and add these commands at the end of the file, just before exit 0 : su USERNAME -c ' mkdir /Volumes/TimeCapsule mount_afp afp://afp_username@server/volumename /Volumes/TimeCapsule ' open /Volumes/TimeCapsule Replace USERNAME with your username on the system. 2. Then add ...


4

TL;DR Use AppleScript, but do not specify the user name or password. Background 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: ...


3

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


3

Synology has a few solutions. Their products are reliable and affordable. There are multiple applications you can install in a few clicks but for S3 backups you will have to go the manual way.


3

You can put aliases to the remote volumes in your Login Items folder. A nice explanation of this feature is available from Apple on the web and the built-in help: http://support.apple.com/kb/ht2602


3

It turned out that the issue was indeed different UIDs though the usernames were the same. From the Apple Support Communities link: borbye: 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 ...


3

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 :(


3

Yes. Set up sharing on REM to share the root directory of the second drive. You can right click and do it from the Finder or go in and manage all shares from the sharing system preference.


3

Radio interference? How many other wifi spots are nearby? How many are using the same channel as you? Does this only happen with AFP or does it happen with other protocols as well (e.g., HTTP, CIFS, etc)? Are you using A/B/G/N? What's the memory usage look like on both systems? Is one (or both) maxed out? The traffic seems very bursty. This could indicate ...


3

You should try the transfer in FTP only because FTP sets it's own "MTU". If this sends files very quickly, you are looking at a TCP fragmentation issue, i.e., you are sending TCP packets too large for the router to handle on it's own. I imagine you can tweak the Mac network settings to force fragmentation to 1500 or less per packet.


3

I have seen this happen when there is already a volume with the given name and the OS needs to create a new name to mount the volume as you can't have a duplicate name -- thus the suffix. The first thing to do is, make sure that you don't have any other volumes with the same name. If you do, perhaps you can rename one or only use one at a time. I've also ...


3

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


3

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


3

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


3

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.


3

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


2

My advice would be to use NFS. You should also try to manually mount the partition from the terminal, so you can add some options too, like -nolock,locallocks,rdirplus This made my browsing much faster, even over wifi. Cheers


2

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


2

I had the same issue. Also for me it worked on another Mac. It turned out that I had to change the Volumes's group to admin which was wheel befor. So I fixed my problem with: sudo chgrp admin /Volumes


2

I'd go for the obvious - connect the TC to the switch. You didn't say what IP addresses were being assigned to everything; whether the 2 nodes as you currently have them are on the same subnet; what the router is & how configurable... etc. so the simple fix is remove the router from the equation.


2

Properly done you can achieve this by prioritizing one interface over the other. Prerequisites: two different networks (physically and logically) e.g. Ethernet: 192.168.0.0/24 and Wi-Fi 192.168.1.0/24 assign static IPs to the ethernet adapters on the source(s) and the target(s) with a proper net mask. A default gateway is not needed. In System ...


2

You can enable individual access to services for users and groups inside of Server.app 3.0. Select the Users or Groups section from the sidebar, and then click on the user or group that you'd like to configure access for. Click on the action (gear) icon below the list of users or groups, and choose "Edit Access to Services...": You'll be presented with a ...



Only top voted, non community-wiki answers of a minimum length are eligible