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!
Ad Blocking Detected
Please consider disabling your ad blocker for our website.
We rely on these ads to be able to run our website.
You can of course support us in other ways (see Support Us).
Connectmenow4 – ignores Windows SMB share names when mounting to custom directory
(@Anonymous)
Joined: 1 second ago
Posts: 0
Topic starter
July 16, 2023 4:59 PM
Version: 4.0.10 (Build 47)
OS: macOS Ventura
Version 13.4.1 (c) (Build 22F770820d)
Intel x86-64 (64 bits) application
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?
This topic was modified 5 months ago by
Anonymous
Ad Blocking Detected
Please consider disabling your ad blocker for our website.
We rely on these ads to be able to run our website.
You can of course support us in other ways (see Support Us).