[SOLVED] Problems creating SMB mount

ln_willo

Hi,
I am loving the Rune Audio setup. I'm looking at incorporating it into a multi room audio setup I've got in the pipeline. I'm just having some issues mounting a SMB share to a Windows 8 PC.
I've created a share on the PC which I can access from other PCs fine. I set up the SMB mount on Rune Audio with the appropriate username, password and path details, but when I check on it, it shows the following error: sh: ,sec=ntlm,soft,uid=45,gid=45,rsize=16384,wsize=17408,iocharset=utf8,cache=none,ro: command not found

I then tried giving everyone read access to the folder and resetup the SMB mount with guest access, but I get this error: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Does anyone have any suggestions? I tried adding the sec=ntlm flag to the advanced options, but this didn't work. I can successfully mount a manual share through SSH.

Thanks
Luke

thekoening

same problem

hondagx35

Hi,

it shows the following error: sh: ,sec=ntlm,soft,uid=45,gid=45,rsize=16384,wsize=17408,iocharset=utf8,cache=none,ro: command not found

Command not found means, that there is something wrong with your mount command.
Please post the settings you made on the "NAS mounts" option page.

With guest access i never had luck.

ln_willo

Hi hondagx35,

Thanks for the response. I've set the NAS Mounts as follows:
Source name: MusicCollection
Fileshare Protocol: SMB/CIFS
IP Address: 192.168.1.100
Remote Directory: Music
Guest Access: Off (also tried on)
Username: administrator
Password: mypassword
Advanced Options: Off and not configured

: Mount.jpg (105.69 KiB) Viewed 3641 times

Thanks
Luke

hondagx35

Hi Luke,

your settings look fine.

In conjunction with the error message starting with "sh: ,sec .." i believe there is something wrong with your password.
Does your password end with "sh:"?
If your password contains special characters (like space, colon), please try an other one or put it in double quotes.

frank

ln_willo

Hi Frank,

My password did contain special characters. I created a secondary restricted account with a simple password and it connected perfectly.

Thanks for your help on this one mate. Much appreciated.