Lets be clear in our terminology. A macOS Alias is a file that works with the Finder and GUI applications that call the GUI File Manager Framework.
A symbolic link is a low level file system abstraction that all programs and files can see and use.
When dealing with access the Mac from a remote system and having symlinks, it is important that the symlink path be a path that is visible to the remote system, as many times their view of the world starts from the mount point down.
That is to say if you export /Users/your_username/subdirectory/sub/sub/THIS_DIRECTORY
The remote system can only see things from THIS_DIRECTORY down.
So, if your symbolic link path includes things like /Users/your_username/etc... the remote system cannot see them because they were not exported as part of the mount point.
In that case, you need to use relative paths
Symlink to file in same directory to create a different name
ln -s original_name alternate_name
Symlink to file that is one directory up and then down a directory would be
ln -s ../down1/down2/original_name alternate_name
Need to go up 2 directories and then down
ln -s ../../down/original_name alternate_name
In all of these examples, I have ASSUMED that you are issuing the command from the directory where the alternate_name is located.
If that is not the case, you will need to specify a longer path.
But in all cases the relative path to the original_name MUST assume it is starting from the directory where the alternate_name is located.