Dumb question here, but you did remember to point at a directory to mount the share to, right?
Part from that, I’ve encountered needing to provide the domain as well (typically WORKGROUP) as the credentials for a user with access to the given share.
Furthermore providing username and password on the command-line is known to have some issues, thus I encourage you to provide them in a credential file, which would look something like this:
username=value
password=value
domain=WORKGROUP
My typical command, changed for your case, would be:
mkdir -p ~/mounted_music
sudo mount -t cifs -o credentials=~/creds //DESKTOP-N840KKP/My\ Music ~/mounted_music
Not sure I’ve encountered it myself, but some shares doesn’t support Unix Extensions which can be disabled with “nounix”, you might want to define access rights then either “rw” or “dir_mode=0777,file_mode=0777”. (0777 is not a good practice, but it’ll do for testing) thus something like the following options argument.
Dumb question here, but you did remember to point at a directory to mount the share to, right?
Part from that, I’ve encountered needing to provide the domain as well (typically WORKGROUP) as the credentials for a user with access to the given share. Furthermore providing username and password on the command-line is known to have some issues, thus I encourage you to provide them in a credential file, which would look something like this:
username=value password=value domain=WORKGROUPMy typical command, changed for your case, would be:
mkdir -p ~/mounted_music sudo mount -t cifs -o credentials=~/creds //DESKTOP-N840KKP/My\ Music ~/mounted_musicNot sure I’ve encountered it myself, but some shares doesn’t support Unix Extensions which can be disabled with “nounix”, you might want to define access rights then either “rw” or “dir_mode=0777,file_mode=0777”. (0777 is not a good practice, but it’ll do for testing) thus something like the following options argument.
Yeah, I forgot to make that a part of the comment, oops!
I’ll try your other suggestions when I can.