Unable to add local or network shares - driving me crazy!

Comments

26 comments

  • Official comment
    Bjørn Ulvik
    Hi-Res

    If I try to add my computer manually \\COMPUTERNAME\ it says "mounting share failed."

    Try to add \\COMPUTERNAME\SHARENAME\

  • Turnthegun

    Thanks for the quick reply. I still get mounting share failed.

    0
  • Bjørn Ulvik
    Hi-Res

    Have you tried disabling firewall on your computer?

    Have you tried creating a new user with permission to the share?

    0
  • Seppi Evans
    Hi-Res

    You could try using the IP address of he PC when entering in the URL

    0
  • Turnthegun

    Have you tried disabling firewall on your computer?

    Have you tried creating a new user with permission to the share?

    I haven't tried disabling the firewall. It worked fine before with it and I don't want it off. I also haven't tried creating a new user to test.

    You could try using the IP address of he PC when entering in the URL

    I've tried the IP address as well and I still get the same errors.

    0
  • Bjørn Ulvik
    Hi-Res

    To rule out your network, if possible try connecting the share from another computer after disabling the firewall.

    0
  • Seppi Evans
    Hi-Res

    Could also try ignoring the desktop app and try an Android or iOS device to setup the share.

    0
  • Turnthegun

    Could also try ignoring the desktop app and try an Android or iOS device to setup the share.

    I finally got it to work using the Android app. The only thing that worked was //myipaddress/sharename

    I just don't understand why it stopped working in the first place, and why it's such a pain to troubleshoot this.

    0
  • Seppi Evans
    Hi-Res

    If not already done reserve the IP address for any Bluesound devices you have along with the PC that you use for the music share on your Router.

    Whilst in your Router setting have a look to see if there had been any firmware updates recently. 

    0
  • Turnthegun

    I haven't reserved IP's for my Node's yet (I've got 2) but once it'd done indexing I'll do that. I've got the IP reserved for the PC. I just got a new mesh router and it's all up to date. I'm just hoping everything stays working now. Usually most updates to the Node's cause my library to stop working.

    0
  • Seppi Evans
    Hi-Res

    Should have mentioned the new router in your opening post, good to hear it working now,

    0
  • Turnthegun

    It stopped working prior to the new router. I was hoping the new one would help.

    0
  • Seppi Evans
    Hi-Res

    👍

    0
  • Michael

    The subject is really terrible. WHAT were they thinking? Has anyone thought anything about it. I've been trying to get a connection to my HDD on the Fritzbox for 3 hours. 99.9999999% of ALL apps and tools in the market have the function to find the shares via search. Only BlueSound does not. From the beginning. And despite all the discussions nothing happens. Nothing!!!!! it's just creepy. 4.9 stars for BlueSound in total, and four stars right away away away.


    0
  • Seppi Evans
    Hi-Res

    Michael, with the Fritzbox! you need to use its IP address, e.g.

    \\192.168.178.1\fritz.nas

    0
  • Michael

    Thanks, that would be exactly what I suspected .... but doesn't work.... all path combinations don't work.
    It took me 20 minutes today to set up a HDD on the FBox for Kodi ... ALL media and configuration. But BluOS does not find anything with the self-offered button to search?!?? Sorry if I repeat this so clearly. Every app I have that provides network access finds the drive. Android, iOS, iPadOS, MacOS etc. ... What is this BlueMagic ;-) This is buried!

    0
  • Seppi Evans
    Hi-Res

    I have a 7530 and it works OK for me, granted its not the best or fastest NAS going.

    Apart from using the path I posted above I made a note that it (In the Fritzbox! settings) needs a user configured, NAS turned on and access granted.

    Suggest you powercycle the Fritzbox! and then your Bluesound device and try again.

    0
  • Michael

    Thanks for the tips, I appreciate it. I do have a user in the FBox and with access to the content, etc.. I already had to do that because of the setup for Kodi. And that goes flawlessly.
    I'll find an old hard drive and connect it directly. That might work. If BlueSound has not developed a "new USB special format" and I first have to format the disk with Linux.... or some such chaos. I still find it weak. Have already no desire to the Pulse+ ... since the HDMI input does not find the TV maybe? ;-) You realize, I am very disappointed that nothing improves. Since Windows 3.1 was even smarter ;-)
    That's enough for today. This costs me far too much time

    0
  • Gord Metcalfe

    I had the same problem, drove me nuts for three days until I saw this forum and noticed the suggestion of making the attempt on a different device. I had been using the Windows desktop BluOS app, and after seeing this page I attempted it on my iphone and it finally worked. Thank you thank you thank you! 

    1
  • Terje Skjærpe

    I have the same problem. I am new to Bluesound (Node). My previous experience is from Sonos Connect ver 1. Then I had no problems adding local or network shares. With Bluesound I find no way to add a local and a network share on my Windows 11 laptop. So far no luck even with a Galaxy Tab S8, Android version 14.

    I have followed your guide on how to enable file sharing with no success. I have some experience with network setup and file sharing between computers. I use a Windows 10 PC as a file server. I use Deco mesh routers. So far it is a mystery why it should be so difficult with the Bluesound app.

     

    0
  • Gord Metcalfe

    This process can be so frustrating, I know. As a last resort, open a ticket with support. They are usually pretty good about getting back to you within a day.

    0
  • Gordon Delgado

    Networking is hard for most people. Adding a network share is full of gotchas, and the recommendation to use fixed ip addresses or ip reservations in dhcp goes way beyond most people's skill levels. The potential for digging yourself into a deep hole is immense.

    The CIFS client being used by bluos is most likely a tweaked samba client. Using this to communicate with a windows share is tricky even when you are not using a 'black box' like the bluos box, which gives you no access to logs for troubleshooting. In addition, Microsoft is locking down windows shares because they represent a software vulnerability.

    So if you are attempting to access a network share, don't feel too bad.

    You don't say whether you are using anonymous access or password protected share. If you are using anonymous access, Google for 'enable anonymous access to windows shares'. Beware, it's also very hit and miss. Also make sure that the share is read only!!!
    In any case, I would recommend setting up a windows or mac computer on your network and trying to access the share that way. If you can do this, you are most of the way there.

    0
  • Terje Skjærpe

    Thanks for a quick response.

    I am running the Bluesound from a laptop. It has enough free space to accommodate my networked music folder. Would it be easier to add it as a local share?

    0
  • Terje Skjærpe

    To be sure I didn't miss any steps in the Network file sharing guide from the Bluesound.com site, I picked up my Tab S8 once again and followed the guide painstakingly. It worked. IT WORKED!  And miraculously, when I went to my Windows laptop, the share was also there. It just needed another reindexing.

    Thank you guys for your kind responses.

    2
  • Carlos Rodriguez

    I have the same issue every time there is an update to the desktop app. I have NODE 2i  and i have spent many hrs trying to have the iTunes Library play on the Node with very poor results. Sometimes it does, most of the time it doesn't play. it is the worst system i've ever bought. I put a service ticket and after a week no follow up. I had this Node for 3 years and it is going right in the GARBAGE.

    0
  • Gord Metcalfe

    I’m not an expert by any means but I have some experience with Node since 2017. Support set up a fixed IP address for me at one point which solved my connection stability problems. Sorry to hear support is not being responsive. I have never waited more than 24 hours. I suggest you check their phone support hours and call the minute the desk opens in the morning and you might get a tech on the phone, which is ideal for expediting a solution.

    0

Please sign in to leave a comment.