· None of the above quite fits
· None of these quite match
· I cannot move music files from Synology NAS to new drive installed in Nucleus
· unifi router, unifi switch, all hard-wired,
Not knowing what the details are for the issue you are having, try reading this and see if it helps:
this all sounded great at first (and seemingly exactly what I was looking for) - but here’s what happened: The \\NUCLEUSONE\Data\Storage\InternalStorageworked great, and it asked for login, I tried guest but that was blocked (exactly as shown in the image) so I tried the Group Policy Editor, and the first step went fine, but there was no trail to get to the SMB. So I went back, and now File Explorer gives me an error when I try to connect to storage.
Also, the other method of drag-and-drop looked promising, but all my music already shows up because I already connected to Synology, but they are pointing to the NAS files, and not actually on the Nucleus.
I’m confused
If you are moving all the music to the drive on the nucleus you will probably want to disable the NAS storage location on the Nucleus before you start transferring the files. So that the database does not get confused with all the duplicate files.
I am on Linux right now so cant really help with the windows access issue.
You might try the alternative option of mapping the drive shown toward the bottom of the KB linked above? You might also need to state which OS you are using to transfer the files (win10, win11, home or pro)
mapping drive doesn’t work either.
It’s Windows 11 Pro
Did you follow these points from the FAQ linked above? One of them might work.
For Windows Pro / Enterprise (using Group Policy Editor):
Press Win + R, type gpedit.msc, and press Enter.
In the Local Group Policy Editor, navigate to: Computer Configuration > Administrative Templates > Network > Lanman Workstation
Double-click Enable insecure guest logons.
Set the policy to Enabled, then click OK.
Still in the Local Group Policy Editor, navigate to: Computer Configuration > Administrative Templates > Network > SMB Client
Double-click Allow insecure guest logons.
Set the policy to Enabled, then click OK.
For Windows Home:
Since Group Policy Editor is not available by default, you’ll need to use PowerShell:
Press Start, type powershell, right-click Windows PowerShell, and choose Run as administrator. Accept the prompt.
To disable the SMB signing requirement, run:
Set-SmbClientConfiguration -RequireSecuritySignature $false
When prompted, type Y and press Enter.
To enable guest fallback, run:
Set-SmbClientConfiguration -EnableInsecureGuestLogons $true
Again, type Y and press Enter.
There is no heading for “SMB Client” under Network (nor under the next Network heading within Network)
Computer Configuration > Administrative Templates > Network > SMB Client
Hey @Ric_Parker,
Thanks for writing in and for sharing your report!
The missing “SMB Client” node is expected on stock Windows 11 Pro, that ADMX template isn’t always present, and it isn’t required.
Instead, skip gpedit entirely and run both settings via PowerShell instead, which doesn’t depend on the policy templates existing. Open Windows PowerShell as administrator and run:
Set-SmbClientConfiguration -EnableInsecureGuestLogons $trueand
Set-SmbClientConfiguration -RequireSecuritySignature $falseconfirming Y at each prompt.
The “Enable insecure guest logons” policy you already set under Lanman Workstation may also need a reboot (or gpupdate /force) to take effect.
After that, retry \NUCLEUSONE\Data\Storage\InternalStorage and choose Guest when prompted.
A cleaner alternative worth offering: rather than fighting SMB guest access, point Roon Server to the internal drive as a watched folder and let Roon copy.
But the more robust fix for what you’re actually trying to do, get files physically onto the Nucleus, is to confirm @bearFNF earlier point first: disable/remove the Synology NAS storage location in Roon Server settings before transferring, so the database doesn’t index NAS and internal copies as duplicates.
One clarifying question is worth asking, because it changes the answer: is the goal is to physically relocate the files onto the Nucleus SSD, or just to have Roon Server play them reliably? If it’s the latter, the NAS path already works and no file move is needed.
Thank you!
Thanks for the input:
The PowerShell changes had no effect.
I guess I’m missing where to do either of the other items you mention.
What I want to do is get rid of the ancient Synology NAS and have the songs just on the Nucleus.
It still seems odd that at one point I saw the login page for guest (like the earlier image showed) but then never again.
Hello @Ric_Parker,
Please follow our step-by-step guide for enabling SMB guest access on Windows:
Enabling SMB Guest Access for Roon Nucleus / ROCK on Windows
The guide covers all Windows versions and includes an important additional step - disabling SMB Signing - which may be why the PowerShell commands alone did not work. Please also check if the error code you are seeing matches 0x80070035 or 0xc000a000, as the guide identifies both.
After making the changes, reboot your PC and try connecting again.
Windows may have cached incorrect credentials for the Nucleus share, which would explain why the guest login prompt stopped appearing. Let’s clear those first:
Open Control Panel → User Accounts → Credential Manager
Click Windows Credentials
Look for any entries containing NUCLEUSPLUS, NUCLEUS, or 192.168.x.x (your Nucleus IP)
Click on each one and select Remove
Reboot your PC
Try connecting to \NUCLEUSPLUS\Data\Storage\InternalStorage again - the guest login prompt should reappear
Could you also let us know what exact error or prompt you see when you try to connect? A screenshot would help confirm whether the change took effect.
Nothing with Nucleus or its IP is there
“Windows cannot find \NUCLEUSPLUS\Data\Storage\InternalStorage. Make sure you typed the name correctly, and then try again”.
FYI - it’s a Nucleus One, so I tried the above and also replaced “PLUS” with “ONE”, and I get the same thing.
I restarted the unit and tried again as well
Again, this worked once.
I thought this was going to be simple 
Hello @Ric_Parker,
The error “Windows cannot find \NUCLEUSONE” means Windows cannot resolve that hostname via DNS - your router may not have a DNS entry for it.
Please try connecting using the Nucleus One’s IP address directly instead of the hostname:
192.168.1.1) and look for the Nucleus One in the connected devices list
\\192.168.x.x\Data\Storage\InternalStorage (replace 192.168.x.x with the actual IP)
ping NUCLEUSONEand share the result? This will confirm whether the hostname resolution is the issue.
the file explorer connection worked fine
the ping is very odd, as it gets about three lines and disappears (closes) so quickly I finally had to take a picture to see what it said:
Pinging NucleusOne.local [10.0.68.96] with 32 bytes of data:
Reply from 10.0.68.96:bytes=32 time=1ms TTL=64
Hello @Ric_Parker,
Great news - the IP address connection works and the ping confirms your Nucleus One is healthy at 10.0.68.96.
The reason the hostname \NUCLEUSONE didn’t work is that Windows was looking for it via DNS while the Nucleus uses mDNS (.local) for hostname resolution - which is why ping NucleusOne.local worked but \NUCLEUSONE did not.
For File Explorer, simply use the IP address going forward: \10.0.68.96\Data\Storage\InternalStorage
We would also recommend setting a DHCP reservation for this IP address in your router settings so the Nucleus always gets the same IP and this path never changes.
that worked, but it sure seems like that info should be easier to find as you make it sound like it was a simple (and expected) issue.
Anyhow, thank you everyone for chiming in.