Windows security warning during Nucleus connection (ref#STGC4F)

What’s happening?

· Other

Describe the issue

Windows security warning comes up when try to connect to Nucleus

Describe your network setup

Desktop Win 11 connected via ethernet cable to Nucleus. I have a shortcut to "see" the Nucleus: \\Nucleus\Data. Post a major Windows update, when I click on the shortcut, I get an objection-requiring network credentials--a user name and password. I've tried my WiFi credentials but they don't work. I've tried "Guest" for both. No help. I have a screenshot and am delighted to provide. Note: the Nucleus itself works FINE. I am able to listen to music. The "backdoor" http://nucleus.local/ link shows that the Nucleus is healthy. I want to ADD music to the Nucleus but can't now that there is this security roadblock. Thanks for your help!

Hi @Anne_Emerick,
A recent Windows update changed the rules around connecting to SMB shares. It no longer allows anonymous connections. This comment here should help you out

Login prompt when accessing ROCK from Windows (ref#0DPKFY) - #3 by Suedkiez.

Please let us know if you have anymore questions!

Hello Daniel,
Yes, my computer had a recent Windows update. Indeed it was Windows 11 24H2 update.

I went to https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300.
Here are the instructions:

  1. Enable SMB signing in your third-party NAS. Your vendor will have steps to do this online if it’s possible in the device’s management software.
  2. Disable guest access in your third-party NAS. Your vendor will have steps to do this online if it’s possible in the device’s management software.
  3. Enable a username and password in your third-party NAS. Your vendor will have steps to do this online if it’s possible in the device’s management software.
  4. Upgrade your NAS if you cannot enable signing, cannot disable guest, or cannot use a username and password. The NAS will usually have an upgrade option in its management software, possibly labeled as “firmware update.”
  5. Replace your NAS if you cannot upgrade your NAS software to support signing and credentials (you will need to use steps 6 and later to copy your data off of it to your new NAS first)
    Note: I am a network neophyte.

I used Windows Features On and Off to TURN ON the three SMB boxes. REboot. Then click on my Nucleus shortcut. I get the same error.

When it says THIRD PARTY software, doesn’t that mean ROON?
I already tried entering my username (which is my email) and ROON password in this credential box --that didn’t work either.
I need further explainations/details of how to resolve the issue.
Thanks for your help!
Anne

Is this a computer provided by your employer? The message in your screenshot implies that. If that’s the case Roon may not be usable on that computer. It’s possible if you contact your IT department that they could help you out but I think your best bet is to use a computer that you own.

Hi Daniel,
I am retired. This is my personal computer. I understand I have Admin access to my computer.
Roon has been running fine for the last couple of years.
I need deeper help.
Thanks

Okay in that case this should be fixable. To fix SMB security permissions on a Windows group, access the properties of the shared folder, navigate to the “Security” tab, then modify the permissions for the specific group by adding or adjusting their access levels like “Read”, “Write”, or “Full Control” depending on your desired access level. Please let me know if this helps you out or you need more clarification.

I could use the “backtrack” feature to move to a System set point that was before the update. That would probably do the trick. BUT it would be a temporary fix. ANY future Windows update would put me back in the same spot, not being able to see folders on my Nucleus.

IF I have to deinstall and start from scratch, I’m willing. However surely there is some network setting that can be undone?
Standing by…
Anne

Hi Daniel,
I want to my Music folder, and right clicked, >Properties>Share. Set it for everyone for read and write. Reboot.
No help. I still get the Windows credential problem.

I went to the Network area --looks like the latest Windows update put in a password requirement. I turned it off. Reboot. No help.

There is another problem, reported by the Roon software that I want you to be aware of. The path to my music folder is in RED.


Note: All my music is in duplicate. In the Music folder on XP AND in the Storage folder on the Nucleus.
In Roon software, only the Nucleus is listed. When I try to add a new network folder, there is an obbjection.
Note: This RED path problem has been around for weeks. Even so I am able to listen to Roon music just fine–as the music comes from my nucleus.

So I have two problems. The largest FUNCTIONAL problem is this NEW demand for permission to communicate with the Nucleus.
Thanks for your help.
Anne

I have SOLVED the problem. The Windows security/credential screen is 100 due to the latest Windows update -for Windows 11 24H2.
There IS a fix but it has not been released as of Nov 26 2024:
Releasing Windows 11 Build 26100.2152 to the Release Preview Channel | Windows Insider Blog

My temporary solution was to backtrack to an earlier version. System Restore was not a help because it had only one restore point, Nov 25, which is AFTER the Windows update.

I consulted Dell, and was advised that there is a method to GO BACK to a setting just prior to the previous update.

  1. Click on the Windows icon button.
  2. Entery Recovery options (NOT just recovery)
  3. From the list of at least 10 options, select GO BACK.
  4. Proceed from there. Note: there is a warning that you must know the password for you Windows computer. (Dudh!).
  5. The restore took about 10 minutes.
  6. I then clicked on my SHORT CUT to the Nucleus and voila–I am able to SEE the files on the Nucleus. There is NO warning screen demanding a username and password.

I then went to the Windows Update area and PAUSED updates until the end of Dec. Hopefully the pre-release noted above, will be implemented at that time.
Hope this helps others. Getting that warning screen after the Windows update was a pain.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.