Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: Cannot connect NAS
#11
At the risk of asking the obvious, have you tried guest access?

By this, I mean configuring the SMB server to allow guest access to the share(s) in question and then telling moode the Userid is "guest" (case doesn't seem to matter) with no, e.g., blank password.

As an aside, I also have tested mounting SMB shares which do not allow guest access. Works a treat for me. What trips up some here is that SAMBA maintains its own list of user passwords for security reasons. It can be configured to sync them with the system's user passwords but that is not a requirement.

My experience has been that less is more in setting up a SMB server. I usually accept the default configuration when I install the package on a Linux host and customize individual shaves only as needed. I haven't had to fiddle with protocol version settings in a long time (MS WIndows is/was usually the b*stard to deal with)..

If you look at moOde's /etc/samba/smb.conf you'll see a reasonably minimalist setup including the individual share parameters.

Regards,
Kent

PS -

Here's what I get from one of my moOde players using only guest access and no advanced setting changes.

Code:
rho@sunroom:~ $ mount
...
//OMV1.local/Music1 on /mnt/NAS/OMV1-Music1 type cifs (ro,relatime,vers=3.1.1,cache=none,username=Guest,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.0.45,file_mode=0777,dir_mode=0777,iocharset=utf8,soft,nounix,mapposix,reparse=nfs,rsize=61440,wsize=65536,bsize=1048576,retrans=1,echo_interval=60,actimeo=1,closetimeo=1)
...
Reply
#12
Thank you for the tips. I have tried guest accounts, but without any luck. I just noticed that the NAS share is available on my network, and that I could connect to it. So I will look at the smb.conf on moOde as you suggest.

The example that you shared has a lot more options than mine. I guess that it is because it's from a much later version (9.3?). Because I have several pi zero's I am running 8.3.9.

I am pretty certain now that it isn't anything at the moOde side of things. Sorry Sad It must either be something with my Samba server (most likely), or there is something else about how my local network is configured that is causing the issue.
Reply
#13
PROGRESS!!! I copied the smb.conf from moOde to my server. Thanks Kent, I don't know why didn't I think of that earlier :/ It now (half) works. Authentication still fails on my main shares, but I managed to add a read only share of my music with guest access. I am now rebuilding my music database... which on a Pi Zero is going to take some time Big Grin

As with most problems, it looks like there were actually two problems, as there is an issue on my local network and nebios. But I will sort that later. I can access my music again. I really thought this was an issue with moOde, not with samba and my network. So sorry for posting here, but massive thanks to everyone for the help. I couldn't have got this working without your help. Thank you! Now I can get on with the fun stuff, and not to mention enjoy using moOde Smile
Reply
#14
(03-28-2025, 02:23 PM)pagandan Wrote: in dmesg I now get the following errors :

[ 4634.469659] CIFS: Attempting to mount \\192.168.1.50\mynas
[ 4634.484905] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
[ 4634.485049] CIFS: VFS: \\192.168.1.50 Send error in SessSetup = -13
[ 4634.485136] CIFS: VFS: cifs_mount failed w/return code = -13

The login credentials are correct, I've even added and tried to use different shares and different users. But for some reason I just can't logon?

On my end a cifs mount looks like this in dmesg. Note the forward slashes.

Code:
[13553.813120] CIFS: Attempting to mount //MOODE/NVMe
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#15
(03-28-2025, 04:46 PM)Tim Curtis Wrote:
(03-28-2025, 02:23 PM)pagandan Wrote: in dmesg I now get the following errors :

[ 4634.469659] CIFS: Attempting to mount \\192.168.1.50\mynas
[ 4634.484905] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
[ 4634.485049] CIFS: VFS: \\192.168.1.50 Send error in SessSetup = -13
[ 4634.485136] CIFS: VFS: cifs_mount failed w/return code = -13

The login credentials are correct, I've even added and tried to use different shares and different users. But for some reason I just can't logon?

On my end a cifs mount looks like this in dmesg. Note the forward slashes.

Code:
[13553.813120] CIFS: Attempting to mount //MOODE/NVMe
 
The message CIFS: VFS: cifs_mount failed w/return code = -13  just means "permission denied", but its presence also means the driver did reach the server.

As in Tim's case, on a moOde 9.3.0 player I see logged to the journal

Code:
sunroom kernel: CIFS: Attempting to mount //OMV1.local/Music1

Had the mount failed there would be more.

Regards,
Kent
Reply
#16
How do I mark this as solved please?
Reply
#17
(03-28-2025, 05:43 PM)pagandan Wrote: How do I mark this as solved please?

Go back to your first post. Select Edit>Full edit. Select the prefix you want in the header box. Save. Done.

Regards,
Kent
Reply


Forum Jump: