Note: These settings can be found under Advanced Options for each individual share.

The default macOS way

Set "Mount Style" to "System Call".

When setting "Mount Path" to "Default"  then macOS by default uses the directory name of the share you're mounting (or better said: the share name as it is presented by the server, which typically is the directory name on the server).

This is how macOS will do it in Finder as well.

Example mounting "MyShares" on a server will result in "/Volumes/MyShares".

Custom Path options

Set "Mount Path" to "Custom Path".
The reason to do this is that custom mounts in "/Volumes" are not allowed by macOS.
So this will always replace "/Volumes".

1. Replacing "/Volumes"

This allows us to mount shares anywhere we like.
Meaning: using a different path instead of the default "/Volumes".

I often use "~/MountPoints".

Since it behaves like macOS default mounting, it will create a subdirectory for each mount.

Example mounting "MyShares" on a server will result in "/Users/hans/MountPoints/MyShares".

2. Replacing "/Volumes" and using a specific path name for a specific mount

Second option is to define a specific directory for just one share to be mounted.
So NO subdirectory will be created and this path should be used for only one specific share.

Example mounting "MyShares" on a server will result in "/Users/hans/MountPoints/SomeRandomName".

It's possible that this behavior is specific to how Connectmenow4 handles mounting shares to custom directories, and there may not be a straightforward solution within the application itself. However, there could be workarounds or alternative methods to achieve the desired behavior.

One approach could be to create symbolic links within your custom directory that point to the shares mounted in /Volumes. This way, you could maintain the custom directory structure while still leveraging the correct share names for the sub-directories.

Another option might involve scripting or automating the mounting process using a tool like Automator or a custom shell script. This could allow you to control the naming of the sub-directories more precisely and ensure that they reflect the share names rather than the local paths.

If this issue persists and is causing significant inconvenience, it might be worth reaching out to the developer or support team for Connectmenow4 to see if they're aware of the issue and if there are any plans to address it in future updates.

In the meantime, sticking with mounting shares to /Volumes might be the most practical solution, but I understand your preference for using a custom path. Hopefully, with some exploration and experimentation, you'll be able to find a workaround that meets your needs.

When I mount shares from my Windows 10 machine via SMB in /Volumes, Connectmenow4 names the sub-directory for each share using the share's name (e.g., MP3) as expected. If I instead mount the same shares to a custom directory (e.g., /Users/first.name/Mountpoints), Connectmenow4 names the sub-directory using the share's local path on the Windows server (e.g., /C/Users/username/Documents/Music/MP3) instead of its name, and multiple share mounts with the same initial path (e.g., any share that starts with /C/Users/username/Documents) end up overwriting one another.

I'm using /Volumes for now, but would much prefer to use my custom path. Is this a replicable issue for anyone else?