· I'm trying to access internal storage using a Microsoft Surface Pro (windows 11). I want to copy over a great many files from my network server so drag and drop is an inferior option. I can access the web interface at \\NucleusTitan but can't access the internal storage that way at NucleusTitan\Data\Storage\InternalStorage. Nothing responds. So I tried to add this as a mapped network drive and I get a popup asking me for network credentials. I tried the Set-smbclientconfiguration fix suggested by your website (set RequireSecuritySignature to $false and then set -EnableInsecureGuestLogons to $true and both commands run ok and I respond with a Y - but i still get the popup asking for network credentials. (And by the way, does that fix make my network less secure)?
Tell us about your home network
· Spectrum network, eero being used as router and a cisco switch. No problems finding the Nucleus.
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:
To Answer Your Security Question:
Please don’t worry—running those PowerShell commands does not make your entire home network less secure. Microsoft disabled insecure guest logons by default in Windows 11 as a broad compliance measure to prevent PCs from connecting to malicious network shares in public environments. Because your Nucleus sits safely behind your home router/firewall and doesn’t hold any sensitive personal data, enabling this setting on your Surface Pro carries virtually zero real-world risk, provided you aren’t using your Surface on untrusted public Wi-Fi networks. Your home network remains perfectly safe.
If you are still concerned, we have completely upgraded our backend file-sharing engine from the legacy Samba 1 stack to Samba 4. As part of this modernization, RoonOS 3.0 now supports a standardized credential handshake to easily satisfy Windows 11 security policies without requiring users to mess with registry keys or group policies.
Please give those steps a try and let me know if you are able to connect afterwards!