Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
Hello,
I'm new to Mac OS and recently learned that volumes have a tendancy to un-mount. That's how I stumbled upon here. I'm trying to have my Synology NAS auto remount and I'm having an issue setting this up. I'm currently on SMB Share on my NAS as well.
I've entered the server address on my NAS and the Ping is successful. I selected the Path but left the Domain blank. I've entered in my user name and password and when I test mount, nothing happens.
I'm using the new Mac Mini M4 with the latest OS if that helps.
I'm not sure what I'm doing wrong.
Thanks
Hi im_butters!
Apologies for the very late response.
Sounds like you entered the settings correct.
An example for my NAS:
You can try the "Show log" option to see of error occur - feel free to post the output here in the forum (consider removing private information if it lists any).
I'm having the same issues. Was this ever resolved?
The user never replied unfortunately.
What comes to mind - as far as I know, the Synology NAS has a build in firewall. If your NAS is not exposed to the Internet then you could try and see what happens when you temporary disable that firewall (if it was enabled).
Another thing: if your Synology is rather old, it may be using an older Samba implementation, which could mean that password encryption becomes a problem since macOS no longer supports the old way (SMB v1 I believe).
Does your NAS mount in Finder properly?
If so: can you post the output from "mount" in Finder?
(remove irrelevant info and maybe modify visible usernames/password)
On that note: I have a QNAP NAS (comparable to Synology of course) and have not encountered this issue.
