I have recently purchased a laptop with Windows 11 Pro (25H2) and am having trouble finding \Rock\Data on my home network.
I regret that the page referred to above is out of date and needs to be updated. I have installed SMBv1 but the Enable insecure guest logons page no longer exists. If only it were so simple!
As far as I can see, the permissions may now be covered by four Local Policies:
User Rights Assignment:
Deny access to this computer from the network. Default: guest
Security Options:
Accounts: Administrator account status. Default: disabled (I am the sole user and Administrator)
Guest account status. Default: disabled (but I have set this on)
The latter rule is stated as interrelating with:
Network access: Sharing and security model for local accounts. Default for standalone computers: Guest
Try as I might to map a network drive and assign a drive letter with sensible combinations of these settings I keep getting the message that guests are barred due to the security settings.
Any new advice needs to include whether to use Guest/guest as the user name and p/w and also whether to click “Connect using different credentials” in addition to the obvious “Reconnect at login”.
This matter is evidently quite complicated and so could Roon please look at this as well as end-users?
It sounds like you’re running into a known issue caused by Microsoft tightening security. You might have to perform a few extra steps to tell Windows that it’s OK to connect to your ROCK system.
I have carried out steps 7 & 8 in the MS advice page because I have Windows 11 Pro, but assumed that I did not need to carry out step 8, needing some actions in the terminal, because my reading of it suggested that this might help someone with Windows 11 Home. Is this correct?
I have rebooted etc., but still get the * You can’t access this shared folder because your organization’s security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network" message when I try to map a network drive.
Please also clarify if we still need to install (or now take out again) SMBv1 and whether the “Guest” user name and password still holds, all as per the existing Roon advice page? The latter surely needs attention.
When I was trying to solve the issue of no longer being able to access my streamer (running Roon Server) from my Windows 11 (Home version) computer, I found that having SMBv1 didn’t seem to matter. Having SMBv1 on or off didn’t make any difference.
Following the steps in the link posted by @Rugby resolved my issue. Granted, I was using the steps for the Home version, not Pro.
(ROCK has supported SMBv2 for many years and it’s all documented in Roon Software Discussion > Software Release Notes but I’m getting tired searching for and posting the same things over and over again )
Erm - you should do steps 6 and 7 using the Group Policy editor if you have Windows 11 Pro, and not steps “7 and 8”…
If you are still getting this message, then I would double-check that you have done the necessary steps given in the article correctly. The message is telling you that you have not successfully enabled insecure guest logons.
And yes, SMBv1 is not needed (and personally, I would remove it from your Windows installation) and the guest username and password still holds.
Thanks to all for your suggestions and clarifications, yes, sorry, it was steps 6 & 7 I carried out. I rechecked and I hadn’t completed 7 properly. However, I am still getting the message.
This is not critical for me as I can get to the ROCK InternalStorage etc. via smb on older computers, namely a Toshiba running Q4OS/Trinity (Debian) Linux and a Macbbook Pro 2013. I have given up and reverted to the defaults on the new Windows 11 machine. However, I would make two points:
The help page referred to in the title has been out-of -date for at least six months, since Windows 11 24H2 reached general release. In line with its usually immaculate technical profile, could Roon Technical Support please sit down with a Windows 11 Pro computer and reissue the page with tested workarounds?
Both the SMB system that Debian Linux is perfecting, smb4k, and the Windows 11 one, both featuring user name/password access, do not, in my experience, see the ROCK server on the network at all. Surely, due to the ubiquity of Windows 11, Roon will have to fall in line and modify its operating systems so that access to them is via the more secure and up-to-date method?
That is very odd, because step 7 is the crucial one and it should have resolved your issue. There must be some other conflicting setting in Windows that is preventing this from working but I’m sorry I don’t know where to point you…
I have gone back to this and got it working in Windows 11 Pro 24H2/25H2.
In addition to steps 6 and 7 in the above MS advice, you need to change settings as follows via Local Security Policy (type this in taskbar)/Security Settings/Local Policies/Security Options:
Accounts: Guest account status > set to Enabled
Network access: Sharing and security model for local accounts > set to Guest only - local users authenticate as Guest
Then map a network drive in This PC, entering a drive letter and the path \ROCK\Data (two backslashes before ROCK, only one is appearing in this text box).
As well as having Reconnect at login checked as standard, also check Connect using different credentials. After clicking Finish, enter Guest as user name and password.
The drive is available in This PC, but ROCK still does not appear in Network, I gather because MS’s method of network discovery is not supported by Roon.
Windows File Explorer tends to forget about certain non-Windows devices. Just type \\ROCK into the address field (not the Search field) of File Explorer and it will show up.
Odd that you needed to make these changes to Security Options. I don’t have either of these changed, I only needed to do steps 6 and 7 in the MS article…
)
