Can no longer add network shares (silently fails)

Answered

Comments

12 comments

  • Official comment
    Tony W.
    Product Support Manager

    UPDATE ALL!

    Thank you everyone for your patience. 

    Our Quality Assurance Team has identified an issue that credentials are not being passed from the Player to your NAS. This is why Guest is working but secure credentials are not. They have an updated patch from our Product Development Team and our testing and evaluating with hopes of an update in the coming days. I will update you once we have launch confirmation.

    Thank you for your patience and understanding and we do apologise for the inconvience. 

    Please follow this thread for updates and resolution; https://support1.bluesound.com/hc/en-us/community/posts/9517590963607

     

  • Joe D

    I just purchased a Bluesound Node and I am having the exact same error.  During the setup of the unit, it had upgraded automatically to 3.20 version.  Being this is the first time I've done this and not seeing any error messages, I'm not sure what the issue is.  I know the share is working from my Synology since I can access it from my PC using the same credentials as the Node. 

     

     

     

    0
  • Joe D

    I think I have this resolved (at least in my case).  Synology's best practice is to "deactivate" the admin and guest account for security reasons.  It appears that the guest account is required to add a network share to the Node. This is found under control panel->user and group->user on the Synology. So after enabling the guest account and adding the guest user to read only on the shared folder, I'm able to add the network share from the blueos app. 

     

     

     

    0
  • enicandro nuccilli

    Hi,

    I experienced the same issue. Node 2i, Qnap nas, never had a single problem while adding new folders to the network shares through SMB protocol. I lost the entire weekend trying to figure if the problem was the nas (privileges etc), the firmware or the windows desktop app. Things got solved when I downgraded bluos firmware to 3.18.3 version. Waiting the bug to get fixed ASAP.

    0
  • Wim de Nooyer

    I'm having the same problem on my Powernode, it has now 3.20.21 firmware. How do I downgrade my firmware?

    0
  • enicandro nuccilli

    Hi Wim de Nooyer,

    you have to fill the form here: https://www.bluesound.com/?attachment_id=54018

    And then follow the instructions at the bottom of this page: https://www.bluesound.com/downloads/

     

    0
  • Wim de Nooyer

    Hi, I tried that on my Powernode. It won't let me downgrade the firmware either. I extracted the file on different usb sticks, in fat32 and ntfs. I followed the instructions but the firmware stays on 3.20.21

    0
  • Wim de Nooyer

    Ok, I finally managed to downgrade the firmware. But each time I want to use the app it starts downloading the latest firmware and the problem is back! 

    0
  • enicandro nuccilli

    Glad you find the way. Weird thing: my app asks me every time to update but update can be postponed. Anyway, I think that the solution must be found by the bluesound staff. We hopefully keep waiting.

    0
  • Wim de Nooyer

    How exactly do you postpone the firmware update? 

    0
  • Hans Peter Meyer

    I having the same problem with my Node updated to 3.20.21 today.

    Cannot use a privileged user with SMB anymore. This worked before.

    Using guest account works, but this is not what I used before.

    Connects as guest using SMB 3 to Synology DSM 7.1.1-42962 Update 1.

    Please fix.

    0
  • Kada Da

    I have same problem that the blueos app cannot connect the sysnology SMB. Please view log of sysnology setting-file service-smb-view logs. The blueos app still use the SMB1 to connect sysnology and there is no any log. If you change the SMB minimum as SMB2, you will see the rejection due to SMB1 in the log.  

    0

Post is closed for comments.