Nucleus-Naim Nova- 2x Naim muso - Sonos One
I am trying to add a new folder (my NAS drive), but keep getting Invalid network path specified message. tbh I’m not at all sure if the share location if correct… I’m using a mac. How do I locate the correct network path for my Zen Nas?
An SMB network path is \server\drive.
But I expect the problem you are finding is more likely to be that your Nucleus is struggling to get permission for the NAS drive.
There is help here:
And here:
Hi @Sari_Tanskala ,
Were you able to solve the issue with the articles that @Sari_Tanskala shared? If you still need help here, please let us know, thanks!
This is proving too complicated for me. I wonder if there is anyway I could pay for someone to do this for me remotely?
It take it this is an innuos Zen your referring to?
If so then to add a network share you would add in the same path as is used to connect to it to as music.
\\zen\Music or your use the ipaddress of the machine instead of its host name, e.g 192.168.1.2 you can find the ip address from the zen itself or from your router. As it uses guest access you might need to enter guest and guest as the username and password.
https://innuos.com/kb/accessing-the-music-files-on-the-innuos-server/
Yes that’s the Zen, I’ve used the ip address and copied smb:zen/files/music/flac as advised, and still getting the same message Invalid network path specified. I’ve now tried everything suggested above, permissions and configurations. I have no problem seeing the zen nas on my mac or listening to it via my Naim steamer. And it used to work just fine with Roon, so don’t know what’s changed now.
Sorry one thing I’ve forgotten to mention, that this problem arose after Nucleus came back from being serviced last year… (I was not told exactly what was done to it, but I could not get the Boot screen to show up hence it was sent back). Prior to this service I had no trouble with adding the nas.
That is not the correct format of the Network address which should be smb://<hostname>/<shared foldername> so I suspect for the Zen it will be smb://zen/Music
Sorry, same result, I’m afraid.
Hey @Sari_Tanskala,
Ben here following up on your thread. I see from the screenshot you’ve included above - what happens if you grant ‘everyone’ read & write access?
With that, have you tried filling out the username and password as well as the network path?
In your Mac sharing settings, when you have your folder selected, click ‘options’ and make sure ‘Share files and folders using SMB’ is checked:
You can’t do that the share isn’t from the Mac it’s on the Innuos Zen which he is showing as an example of of the path.
Can we take a step back please and ask you to define exactly what it is you are trying to accomplish here?
I thought that you were trying to add the network-shared Music folder on your Innuos server as a Watched Folder on your Nucleus?
If so, then I’m not sure what the relevance of the Mac screenshot is. It would be more helpful if you were to post a screenshot of the Nucleus “Add network share” screen so that we could see the format of the network address that you are using, and the username and password fields. Thanks.
And just to add, I’ve put used anything on the username/password. If I have to, where would I find the username?
Presumably in the manual for your Zen server?
Now confirmed no user/password required. I also just had a local IT service here in London just pop over and look at the issue, they could not see why its not showing up.
The next page of the manual has this:
So shouldn’t the network address be:
smb://zen/Music_readonly or
\\zen\Music_readonly ?
I tried both of those, with same result… invalid network path
I have a slight memory of trying
username: “guest” *
password: “”
which might be worth a go.
I had similar problems trying to share a mac drive - and ending up adding a special user/password for roon. Don’t know if you can do this on the Zen.
The other thing to check is whether the Zen allows you to set SMB compatibility for older SMB versions.
There may also be a log on the Zen or on the Roon core machine in which you can see the actual error.
