Hot answers tagged

2

This is going to be a throughly unsatisfying answer, but it comes down to the fact that random network drives were not meant to be used as time machine backup targets. I'd wager one of the things you did in your guide was to run a terminal command along the lines of: defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1 Unsupported ...


1

In case you haven't found a solution yet, in the guide I was following it never mentioned to run the tmutil utility to set the backup drive via command shell, so just run the following command on a Terminal and you will have the disk selected on Time Machine Preferences: sudo tmutil setdestination "/Volumes/Time Machine Backups/" Remember to change the ...


1

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


1

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


1

What you are really looking for is a smbclient alternative using smbutil but just like you, I couldn't make it work. So what you can do is to install samba with homebrew like this: brew install samba If brew link complains with: Error: The `brew link` step did not complete successfully The formula built, but is not symlinked into /usr/local Could ...


1

As you would have to disable writing of hidden files on every mac that could connect to your share, a better option would be to stop this at the share and not on the clients. All you need to do is to edit your share config (for example in Linux in /etc/samba/smb.conf) and add the following option into your share config: veto files = /._*/.DS_Store/ Now ...


1

Most of the problems I seem to have with this kind of thing come from the ACL rather than the basic permissions. Usually what I end up doing to fix the problem is to format another drive to get the default permissions and ACLs then use these commands to copy them to my old drive: chown $(stat -f%u:%g "$srcdir") "$dstdir" # Copy owner and group chmod $(stat ...



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