01-26-2022, 08:57 PM
The error message
basically means moOde reached the server but asked for a share the server didn't recognize.
[aside]
When using the symbolic hostname of the server it has to be one recognized on the LAN which, depending on the DNS service, may mean having to qualify it. I like taking advantage of mDNS and use <server hostname>.local
Since I reserve IP addresses for well-known hosts like my NAS, my printers, etc., I often mount a share directly using the IP address form: <server IP>/Share_name
[/aside]
As for dirs/subdirs (or folders/subfolders if you like) you should be able to mount the highest level of the share or a sublevel of it.
Example, among other things my NAS shares directory Test.
I can mount 10.0.0.2/Test and access everything in the share or mount 10.0.0.2/Test/SubTest and access only the files at or below the directory SubTest.
If I mistakenly try to mount, say, 10.0.0.2/Test/SubRest, I get exactly the message you got.
BTW, I'm always wary of spaces in file or directory names. It should be ok, but....
Regards,
Kent
Code:
20220125 202900 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
basically means moOde reached the server but asked for a share the server didn't recognize.
[aside]
When using the symbolic hostname of the server it has to be one recognized on the LAN which, depending on the DNS service, may mean having to qualify it. I like taking advantage of mDNS and use <server hostname>.local
Since I reserve IP addresses for well-known hosts like my NAS, my printers, etc., I often mount a share directly using the IP address form: <server IP>/Share_name
[/aside]
As for dirs/subdirs (or folders/subfolders if you like) you should be able to mount the highest level of the share or a sublevel of it.
Example, among other things my NAS shares directory Test.
I can mount 10.0.0.2/Test and access everything in the share or mount 10.0.0.2/Test/SubTest and access only the files at or below the directory SubTest.
If I mistakenly try to mount, say, 10.0.0.2/Test/SubRest, I get exactly the message you got.
BTW, I'm always wary of spaces in file or directory names. It should be ok, but....
Regards,
Kent