· I am attempting to add a Network Share. My hardware is Windows 10 Desktop, Nucleus One Server, Synology Diskstation DS 413j. All software on the hardware is up to date. I can access the music files from my desktop and windows laptop using Windows file Explorer.
Thanks for reaching out. Based on your description, it looks like Windows is blocking access to the Nucleus/ROCK internal storage due to its security settings regarding “Guest” access.
This is a common behavior in recent Windows updates (10/11), where the system automatically blocks network shares that don’t require a password. Since Nucleus is designed to be accessible without a password for convenience, Windows essentially puts up a barrier.
We have a step-by-step guide on how to adjust this setting in Windows so you can copy your music files:
Please give those steps a try and let me know if you are able to connect afterwards!
I’ve attempted what you are requiring. Both my windows 10 and 11 indicated that I don’t have gpedit.msc. I’ve never used powershell before. I’ve attached a screen shot of what I’ve done in powershell. Let me know what I do next.
Thanks for the follow-up and additional information @Rick_Falardeau!
It looks like you ran into a few common hurdles with Windows Home editions and the syntax of PowerShell. Because Windows 10 and 11 Home do not include the Group Policy Editor (gpedit.msc), using the Registry via PowerShell is the correct alternative, but the commands need to be exact.
In your screenshot, the error occurred because “enable guest logons” was typed as a command. PowerShell didn’t recognize it because it’s actually the description of the task, not the code itself.
Step 1: Fix the PowerShell Commands
To apply the changes shown in your guide, you must run PowerShell as Administrator. Copy and paste these lines one at a time and hit Enter:
Hi Benjamin, sorry for the delay. Still not working. I believe we are closer because when I attempt to connect now I don’t immediately get an error message. It appears that Roon is atte
mpting to connect to the Diskstation. Now the message is Invalid network path specified. I have attached screen shots to help you figure this out. I tried to add the network share without a userid and password and I got couldn’t connect because I was unauthorized.
Thanks for giving that a try! If possible, can you verify the exact share name?
The Synology shares music from a shared folder, and the name must be exact. In your screenshots the path tried was IP/My Music/Rick. The issue is whether My Music is actually the Synology shared folder name, or if it’s a subfolder inside a shared folder named something else.
On your Windows PC: Open File Explorer → \192.168.2.97 in the address bar. Write down the exact top-level folder name(s) that appear — that is the share name Roon needs. It might be music, Music, homes, or something else entirely. The name is case-sensitive on Linux (which the Nucleus runs).
In Roon, enter only: \192.168.2.97[exact-share-name] — no subfolders yet. See if that helps at all.
If not, let’s see if you can test and create a dedicated Synology User for Roon.
The “unauthorized” error you saw earlier is telling. The Nucleus (running Linux) authenticates differently than Windows does. Windows can pass your cached Windows credentials transparently; the Nucleus cannot — it needs explicit credentials.
In Synology DSM → Control Panel → User & Group:
Create a new user, e.g. roon with a simple password (no special characters, avoid @, #, ! as they can cause CIFS parsing issues)
Give that user Read/Write permission to your music shared folder
In Roon's Add Network Share dialog, enter that username and password explicitly
With that, there are two separate permission layers on Synology that both need to be correct:
In DSM → Control Panel → Shared Folder → select your music folder → Edit → Permissions:
Make sure your roon user (or whichever user you're using) has Read/Write or at minimum Read Only access listed there
Also check Advanced Permissions, ensure "Apply to this folder, sub-folders and files" is selected
If still failing, temporarily disable the Synology firewall and retry.
Got it to work. The root folder was NAS Storage. As soon as that was entered the folder directory for my server was available. Thanks for getting this to work.
