Bluesound, Samba Sharing, Arch Linux

Beantwortet

Ryan Chang

• 26. Juli 2023 23:35

Putting this info here in case someone else runs into the same problem.

I run Manjaro, a rolling release distro of Linux. Core programs are constantly upgraded.

It's on a laptop that doubles as a NAS for my Bluesound Node 2i.

I upgraded my machine, and BluOS stopped accessing my NAS share.

Deleted the share, tried to add it, but "No Shares Found" error.

Thought I was going crazy!

I double-checked my `smb.conf` and found this instruction on 1.3.10:

Latest versions of Samba no longer offer older authentication methods and protocols which are still used by some older clients (IP cameras, etc). These devices usually require Samba server to allow NTMLv1 authentication and NT1 version of the protocol, known as CIFS. For these devices to work with latest Samba, you need to add these two configuration parameters into [global] section:

server min protocol = NT1
ntlm auth = yes

 

Share successfully added.

If you are on an Arch-based or any Linux system where you can access `smb.conf`, please check these lines are added. I believe it is because the Samba protocols on my Bluesound Node 2i are older than the latest version of Samba on my laptop.

 

 

0

• 

  Ryan Chang

  • 28. Juli 2023 03:30

  Interesting!

  Firewall settings double-checked; router updated too.

  Android app: 3.20.5

  BluOS: 3.20.52

   

  The latest post (permalinked here: https://support1.bluesound.com/hc/en-us/community/posts/360051990274/comments/9498443058711 ) includes a screenshot from a log of the user's NAS. The error message reads SMB1 Not Permitted  

  I was getting this error in my log:

  chdir_current_service: vfs_ChDir(/home/avantbored/Music) failed: Permission denied. Current token: uid=1001, gid=1002, 2 groups: 1002 963. 

  0
• 

  Ryan Chang

  • 28. Juli 2023 19:54
  • Bearbeitet

  Yes, I checked all of those settings -- thank you for being thorough in your conversation about this. 

  This whole thing kicked off because my Node 2i glitched and stopped midstream; I had to restart the component, but would not stream. I tried removing/adding the shared folder again, and that's when the no shares found errors began. I proceeded to:

  • Factory reset
  • Reconfigure Samba share (guest access -- sharing settings -- renaming the folder, even)
  • IP address for \\COMPUTER\FOLDER

  None of that worked.

   

  Only the solution described in my first post worked. Perhaps the setting that is really working is 

  ntlm auth = yes

  Rather than the authorization for SMB1. But, again, the post you are referring to describes an error message with SMB1 Not Permitted. I would imagine SMB1 means v1.0?

   

  I would be curious to see if your smb.conf includes that line?

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.