Problems with macOS path on Synology NAS (SMB) I am having issues with macOS where, after mounting a drive it will mount new drives instead of just jumping to the sub-folder path within the mounted drive. 

For example, I'm seeing where I send someone a path for in the "Video" drive on a Synology (smb://HAL9000/Video).  Instead of mounting the "Video" drive (smb://HAL9000/Video) and going to a sub-folder within the video drive labeled "GoPro -IMPORT", it will create a new drive on their desktop labeled "GoPro - IMPORT".  

If I create a new sub-folder within "GoPro - IMPORT" and send them a link to that like (smb://HAL9000/Video/GoPro%20-%20IMPORT/Test), instead of taking to the sub-folder in the "Video" drive that they already have mounted on their desktop, it will create an entirely new drive labeled "Test" on their desktop.  

I've tried reaching out to both Apple and Synology and had no luck with this.  I would appreciate any kind of help/support.
Unfortunately, this is not how macOS works.
SMB or Server Message Block is a Microsoft Windows technology so it stands to reason that sharing links to SMB shares (or as Microsoft calls them, network shares) is baked into the OS.  The UNC share isn't &quot;mounted&quot; like it is in Unix where &quot;everything's a file&quot;.  In Windows, you can &quot;map&quot; a network drive to a share, but in Unix, you have to mount it.
Finder and SMB
When Finder &quot;sees&quot; the smb:// it invokes the mount_smbfs command behind the scenes and creates a mount point in the /Volumes/ sub-folder.  Using your example, the first time you send the link smb://HAL9000/Video, it will issue the following command:
`mount_smbfs //domain;user:password@HAL9000/Video /Volumes/Video`

If that name exists, you will get the following path /Volumes/Video(1) and if that exists, (2) and so on.  Using my SMB mounts on a Synology Diskstation, as another example, I have the share &quot;Network Share&quot; already mounted.  When I try to mount again using &quot;Connect to Server&quot; (⌘ CommandK and just connecting directly to the server with no share specified, you can see that it's greyed out.

That's because it's already mounted.  Issuing the mount command gives us:
$ mount
/dev/disk2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk5s1 on /Volumes/MUSIC (msdos, local, nodev, nosuid, noowners)
/dev/disk4s2 on /Volumes/My Passport for Mac (hfs, local, nodev, nosuid, journaled)
/dev/disk3s2 on /Volumes/FreeAgent Go (hfs, local, nodev, nosuid, journaled, noowners)
//allan@diskstation.home/Network%20Share on /Volumes/Network Share (smbfs, nodev, nosuid, mounted by allan)

The last line confirms it - &quot;Network Share&quot; is already mounted and can't be mounted again.
So why can't I share links?
Because you don't access the file through smb://server-foo/share-bar/filename.txt (ignoring authentication).  You access it by going to /Volumes/Share-bar/filename.txt
The problem with that is /Volumes/Share-name may be completely different for you and me (see above re: existing names).  The only thing you can do is to rewrite the UNC path to let Mac users know which file you're referring to.  Example:
Windows:  \\HAL9000\Video\GoPro - IMPORT\filename.txt
macOS:    /Video/GoPro-Import/filename.txt

The user will then have to manually navigate to that share to get to the file you're referencing.
This is why they created WebDav because now you'll be accessing the file via a universal https:// link which is the same for everyone.  The downside is that if you intend to share with Windows clients, you'll need to implement SSL certificates.  And yes, Synology does support WebDav