SMB1 still active in Bluesound
AnsweredHave found various forum comments on the error:
HOST [IP.Address] failed to connect via SMB due to [SMB1 not permitted]
In my case this is from my Synology NAS log. It is expected because SMB1 is disabled in the Synology OS. I also deduce from forum comments that Bluesound disabled SMB1 some time ago. However it appears that Bluesound is in fact still requesting SMB1 even though the Bluesound devices are successfully connecting via later SMB versions i.e. 2 or 3. Yet, my log is filling with ongoing, continuous attempts to connect via SMB1, this indicates that Bluesound is still trying use this outdated and dangerous protocol. Can you please help me understand what is going on here?
-
Official comment
I access my music library stored on a Win11 PC and BluOS requires SMB1 to be installed in order that my PowerNode can access the library.
-
Same experience here. Library on HDD directly connected to router. Router allows SMB1 and/or SMB2.
If set to SMB2 Windows can connect to share, but BluOS cannot connect and fails with "Error reading folder Host is down".
To connect to the share BluOS requires the router to be set to either SMB1 or SMB1+SMB2. If set to SMB1 Windows fails, because the SMB1 protocol is not enabled in Windows, as it should be.
0 -
In my Synology log I can see that Bluesound is connecting via SMB3
0 -
Maybe BluOS only supports SMB1 and SMB3, but not SMB2.....
0
Please sign in to leave a comment.
Comments
4 comments