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.

Hello Hans,

Thank you first up for your efforts. I have a couple of questions to clarify please.

Apologies for the double up.  Just found the forum. My questions from the home page are related to this, so let's see if we can't get it resovled. 

For info, I am using CMN 4.0.18 – latest on 2 hosts. Intel running Monterey 12.7.6, and M-series running Tahoe 26.2. For ref., for backups I want to mount one share under user <X>, and for productivity, I want to mount all other shares under my MAC
user to a Synology. The Synology is recent enough running DSM 7.3.2.

All mounts work correctly using Finder and the network. I even have an Automator script which mounts these shares at login. Only problem is they keep going away on sleep, hence the attempt to move to CMN. 

The lightning bolt signifies an ‘active’ share, right. On both machines, I only seem to be able to get one share showing as ‘active’ or – in the UI “MOUNTED” at any one time (even your example screenshots above seem to only show one active). It seems to be random as to which share CMN wants to MOUNT.

What am I missing please? Happy to provide logs, but I must be too dumb, cause I can't see any "Show Log" option. 

Hi Jason, (just pasted my reply here)

just to clarify: are both shares a subdirectory of the same share?

Eg. you have a share on your server or NAS, say

192.168.1.1/myshare

And your 2 shares that you’re trying to mount with different users are subdirectories in that share, something like

192.168.1.1/myshare/Share1
192.168.1.1/myshare/Share2

At least that is what it sounds like, as this would conflict when calling for a mount, as the “base” mount would be “192.168.1.1/myshare”, so the second mount with another user could be rejected (by the macOS API) as it is seen as “already mounted”.

I could be wrong of course.

CMN is capable of mounting multiple shares, even if those shares reside on the same Server or NAS, and even with different users.
I do this all the time for shares on my NAS and when testing CMN.
So there must be something else interfering – which I’d be happy to try to figure out with you 😊 

--- having said that ---

Can you provide more info on the shares you're trying to mount?
(eg. feel free to anonymize sensitive details)

Hi @hans,

thanks the response. To answer, no. They are 3 separate "Shared Folders" . e.g.

/NAS/home (The user home dir on the NAS)

/NAS/files (for storage)

/NAS/backup (for backing up laptops)

Indeed, this morning I can see in the CMN "Shares" pane of the dialog, that each defined share has a GUID, and shows not mounted. I hit the "Mount" button at the bottom of the Share list, the folder icon appears momentarily up top then disappears. Briefly thereafter I get an OS notification bubble top right screen stating the mount attempt failed. This is despite me being actually connected to the NAS in Finder.

I've now located the CMN Log Window under the About button - but it is empty. I mean nothing. Not a single entry -even after multiple mount attempts. For info, I am performing these tests at the moment on the Tahoe machine. 

I will test in a few hours on the Monterey box. 

Just got a quick moment to test on the Monterey box. It has maintained the connection to /NAS/backup. But won't mount anything else - again connected to the NAS in Finder. The Intel version doesn't appear to show the GUIDs of the defined shares in the Dialog. 

And just to clarify for future readers - the Log Window doesn't come up under the About button, rather the 'Help & About' option in the context menu of the system icons top right of screen. 

On the Monterey box, it is also empty. Not a single entry. 

OK. Issue Resolved. Thanks the assistance @hans. 

For future readers: to get the Log recording and showing logs, once you get the Log Window up, you need to click the Tools button in that dialog and 'Log messages to Log window'. 

Once I had some logs, I could GPT the errors and determine what was going on. I don't know how much this contributed to my problems but according to GPT;

macOS 26 tightened SMB auth handling, and DSM 7.3.2 is stricter about rejecting partial or legacy auth attempts. When those collide, macOS just throws Error 65.

---

What’s actually happening under the hood

1. ConnectMeNow asks macOS to mount via SMB

2. macOS silently pulls cached creds from Keychain

3. DSM rejects them (even if they look correct)

4. macOS collapses the failure into NetFSMountURL error 65

One of the remedies recommended is to delete all your smb-related Keychain entries and reboot. I did that, but it didn't help. 

In the end, what my problem was I had put my WORKGROUP for the SMB shares into the DOMAIN box, and that was causing the error 65. As I also run internal DNS, I tried the actual domain all the hosts belong to, but still no joy. 

As soon as I emptied the DOMAIN box, it was all good. 

Thanks again @hans. 

Awesome! Things that happen when I'm asleep haha. 😊 

Very happy to see you've got the issue resolved, and thank you for sharing the solution! 👍