[PROBLEM] Windows SMB source sharing question

[Bogler]

Hi all,

Hoping to get some help resolving what could be a Windows setup issue on my end with sharing a music folder with Moode.

O/S: Windows 10 Pro. Created a user and shared the folder (located on an external drive if it matters). User has read/write permissions. User credentials added to Moode (it's not username/password  ). Enabled network/file sharing, set network to private and believe I set up appropriately. 

Alternatively if I can avoid SMB sharing from Windows is there a recommended alternative? Ideally I wouldn't reactivate the old SMB services, but not sure what works best here and how to restrict that to local network only.

It's likely the issue is how I set things up on Windows versus Moode, but not sure.

Thanks so much for bearing with my technical inadequacies!

Mount log:

Code:

Try (mount -t cifs "ip/share" -o username="username",password="password",rsize=61440,wsize=65536,iocharset=utf8,vers=3.1.1,ro,noserverino,cache=none,dir_mode=0777,file_mode=0777 "/mnt/NAS/friendly-name")

Err (mount error(13): Permission denied

[Snoil]

good morning,
maybe it's a question of windows' insecure guest logons as described here
https://moodeaudio.org/forum/showthread....586&page=2
and here
https://learn.microsoft.com/en-us/window...oup-policy

[Bogler]

Ah, that's great. Thanks for finding those links @Snoil! Not sure if this is the same as when Win10 is the host, but could be similar.

Now maybe I have a new question, is there a way to do this without enabling insecure guest login as a wholly different method for sharing music? Who wants to enable insecurity?

If the answer is no from Windows then is my easiest/best answer to get a different drive and do the sharing from one of my Moode's? That would also be fine as long as I have a working spare USB HD lying around

[Snoil]

sharing from moode is great. found by SCAN and the host's moode doesn't need library updates to share new files. maybe that's obvious.
Only drawback might be that you'll need to unplug that hardrive for new files because of the insecure logon I think.
I hope somebody will clarify the windows situation.

[TheOldPresbyope]

@Bogler

That 10-year old laptop (a ThinkPad whose keyboard I adore) mentioned in the 5-year old thread called out by @Snoil is now 15-years old. May it never die!

It still has a copy of Win10 Pro installed as a guest O/S installed in VirtualBox in Linux so I fired that up this morning. I am now sharing music directories from it to my moOde players in two different ways.

1) In my primary Win10 user account, I have shared a music directory "GuestMusic" to guest users with read-only access rights. On the moOde side, in the Remote NAS source creation panel, I manually entered the path (10.0.0.229/GuestMusic), the Userid "Guest", blank Password, and Name "Win10-GuestMusic". I got a green checkmark when I saved this, and the library update proceeded without a hitch. Success.

2) In a new, secondary user account I just created with username "TestAccount" and password <redacted>, I have shared a music directory "TestAccountMusic" with read-write access only to the account holder. On the moOde side, in the Remote NAS source creation panel, I manually entered the path (10.0.0.229/TestAccountMusic), the Userid "TestAccount", the actual user Password, and Name "Win10-TestAccountMusic". Again, I got a green checkmark when I saved this, yada yada yada.

Note: I could just as easily used the symbolic name of the guest host instead of the numeric IP address when defining the path. DIdn't want to muddy the waters with its name.

Note: I almost never fire up Win10 (or the Win11 Pro guest O/S which is also on my laptop). It's quite possible that the "insecure user login" setting was enabled in it five years ago. I just don't remember. I'll try to find time to look later today.

Note: I think Win10 (and Win11, for that matter) client systems make terrible servers for this purpose and in any case I don't want to have to leave a Windows-based laptop or desktop running just so I can play music. Over the years, I have used a variety of SBCs to host servers on my LAN. Currently, it's a Pi5 with an SSD on a PCIe HAT, running OpenMediaVault on Raspberry Pi OS Lite. I spin up other services on it as needed or out of curiosity.

YMMV.

Regards,
Kent

[Bogler]

@TheOldPresbyope that's great... I'm also on a pretty ancient ThinkPad although not sure if it's 10 yet (T480s FTW!).

I do keep a Windows machine running all the time, it's Celeron-based and shouldn't draw too much more more power than my Pi aside from the attached spinning disk. Regardless less than a bunch of other appliances in the house. Compared to my dehumidifier and HVAC nothing really adds up

That said the Windows box for me has other things on it so I don't want to go opening holes so I think better path for me is the Pi and Moode sharing out the file assuming I have another hard drive around with the space. At the moment down to just two Pis both doing Moode duty so would need to share from one of them. If they don't have the horsepower I have an old ThinkCentre mini (original version w/ so I think well over 10 years old) that I've wanted to convert to ChromeOS or a Linux-y box but I don't know whether I have the technical chops for the latter or if the machine is still alive. I think that would also suck down a bit more power than just putting a HDD on the Pi.

[the_bertrum]

OT I know but....
I recently got a T480 off ebay, it's a dream. I've dual booted it so windows is on there, but it is primarily a Linux Mint machine. 16GB RAM bt it rarely uses more than 4!

[Snoil]

there you go. I'm running an old T430u.
@Bogler So did you check if the share mounts processing 1) or 2) of Kent's post?

[Bogler]

#1 & #2 are what I did so those didn't work but I haven't gone to enable insecure logins. Found an old HDD so will share in reverse from the Pi. It's likely insecure logins are the reason. I'm not confident enough in my Windows FW setup skills to enable that just within my local intranet.

[Nutul]

(...) I'm not confident enough in my Windows FW setup skills to enable that just within my local intranet.

It's always in your network. As far as your router is secured against all those bad guys out there in the wilderness of the Internet...