BLUOS 3.20.25 NETWORK SHARE ISSUE

Answered

Comments

13 comments

  • Seppi Evans
    Hi-Res

    Bluesound is a consumer device that uses an flavour of Unix and as such keeping users away from complex networking terminology is probably not such a bad thing but of course someone with a little IT knowledge would like more information. 

    Logs are available to Bluesound support and contain a vast amount of information for them to help troubleshoot. Using a Wi-Fi or Ethernet the connection is visible in the BluOS App, quite simply the Wi-Fi signal / strength is shown if Wi-Fi is being used in Help….Diagnostics, if it’s not show then you are using Ethernet. Bluesound hardware also has a very simple and effective LED indicator at the front, if it’s showing solid Blue then it’s connect to your router and had a IP address allocated. https://support1.bluesound.com/hc/en-us/articles/200271976-What-do-the-different-colors-of-the-LED-signify-

    Suggest you log a support ticket after trying to add a share, using the BluOS app select Help…Send Support Request, this way the logs will be sent to Bluesound support and they will be in touch.

     

    0
  • Jonathan Anderson

    I understand you, and all this could be echoed back to the user setting up the network share.

    -Can't resolve host name

    -Can't reach host

    -No reply

    -Wrong credentials

     

    0
  • Jonathan Anderson

    To address this further, in reply to my support request, the support team, on purpose or accident, sent back the logs from my powernode to me so I could analyse them myself.

    Essentially the same as having direct access to them, but with 3 days turnaround time.

    They also kindly suggested that I do the same thing as could be read from the logs that I tried just before making the support request.

    Sadly, the logs did not indicate if the problem related to issues with connectability, or credentials in a way that I could understand.

    These are the relevant excerts from the logs:

    Feb 18 15:29:41 (none) user.info cp[502]: shareconfig.go:115: adding share: \\192.168.1.202\Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:308: sec=ntlmssp,vers=3.0 //192.168.1.202/Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:316: Mount command failed: exit status 32
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:308: vers=3.0 //192.168.1.202/Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:316: Mount command failed: exit status 32
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:308: sec=ntlmssp,vers=2.1 //192.168.1.202/Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:316: Mount command failed: exit status 32
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:308: vers=2.1 //192.168.1.202/Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:316: Mount command failed: exit status 32
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:308: sec=ntlmssp,vers=1.0 //192.168.1.202/Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:316: Mount command failed: exit status 32
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:308: vers=1.0 //192.168.1.202/Music
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:316: Mount command failed: exit status 32
    Feb 18 15:29:41 (none) user.info cp[502]: smb.go:362: Couldn't mount: \\192.168.1.202\Music
    Feb 18 15:29:41 (none) user.info cp[502]: shareconfig.go:117: sharesChanged = false

     

      344.738751] CIFS: Attempting to mount \\192.168.1.202\Music
    [  344.751553] CIFS: Attempting to mount \\192.168.1.202\Music
    [  344.764999] CIFS: Attempting to mount \\192.168.1.202\Music
    [  344.777459] CIFS: Attempting to mount \\192.168.1.202\Music
    [  344.789421] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers

     

    0
  • Seppi Evans
    Hi-Res

    What’s the make, model and firmware version of the NAS?

    0
  • Bjørn Ulvik
    Hi-Res

    [  344.777459] CIFS: Attempting to mount \\192.168.1.202\Music

    If you are using wrong credentials the output would be:

    Status code returned 0xc000006d STATUS_LOGON_FAILURE
    0
  • Jonathan Anderson

    The files are shared from Popos 22.04 standard sharing with Rygel I believe. Following DLNA standards.

    https://wiki.gnome.org/Projects/Rygel

    LG WebOS TV picks it up the second it's published. No configuration or credentials. Just instant access.

     

    Thanks Björn. I believe it's openly shared, but I also tried with credentials just to be sure.

    0
  • Seppi Evans
    Hi-Res

    I had a feeling it would be something like this…Seriously, buy a real NAS, in the UK they are less than £100 refurbished from WD and use the Raspberry Pi for a hobby and not something you rely upon.

    0
  • Bjørn Ulvik
    Hi-Res

    BluOS don't use UPnP or DLNA. You will need to create a samba share.

    1
  • Matty A

    Hi everyone I have a similar issue and have posted a separate question about it here. Grateful for any suggestions you may have. Cheers

    https://support1.bluesound.com/hc/en-us/community/posts/12673763246743-Cannot-find-network-share-

    0
  • Jonathan Anderson

    So, to conclude this discussion, there is a standard DLNA that other major players support and BluOS has decided not to?

    Bold move.

    0
  • Jonathan Anderson

    Thanks Björn, will try it as a samba share.

    0
  • Jonathan Anderson

    Samba share worked like a charm. Thanks for pointing me in that direction Björn.

    Shared music folder added right into the collection :-)

     

    BluOS add share still fails without explanation on failed name resolution or wrong credentials.

     

    0
  • Seppi Evans
    Hi-Res

    Bluesound does not use DLNA

    0

Please sign in to leave a comment.