Question How do I get my home NAS access back after upgrading to Win 11 Pro 24H2?

[box o rocks]

Help, network newbie here...
After the above Win update, it seems Win will no longer let me access my network storage drive (Buffalo Linkstation LS210D). Win doesn't even seem to see it on the Network. And Buffalo doesn't have any updated software past 2020 on their website. From what I've read, my problem appears to be something to do with Win 11 tightening security. I did go to "Windows Features" and looked to be sure all three boxes were checked under SMB 1.0/CIFS File Sharing Support. But that did no good. Anything else I can do? I'm wayy out of my league here.

Note: I'm on a private network, not public.
I've rolled my other two Win 11 PCs back to ver 23H2, because someone here at Tom's informed me that 24H2 was still likely buggy. And to wait awhile before updating. But I thought it might be OK now "to get back in the water again". Does this sound like something Win will eventually fix, or is this left up to the user to figure out?

 

[kanewolf]

Help, network newbie here...
After the above Win update, it seems Win will no longer let me access my network storage drive (Buffalo Linkstation LS210D). Win doesn't even seem to see it on the Network. And Buffalo doesn't have any updated software past 2020 on their website. From what I've read, my problem appears to be something to do with Win 11 tightening security. I did go to "Windows Features" and looked to be sure all three boxes were checked under SMB 1.0/CIFS File Sharing Support. But that did no good. Anything else I can do? I'm wayy out of my league here.

Note: I've rolled my other two Win 11 PCs back to ver 23H2, because someone here at Tom's informed me that 24H2 was still likely buggy. And to wait awhile before updating. But I thought it might be OK now "to get back in the water again". Does this sound like something Win will eventually fix, or is this left up to the user to figure out?

Do you know which version of SMB the Buffalo used? It is possible that Windows has disabled an old version of SMB for security. You generally can re-enable the old versions -- https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/

 

[box o rocks]

Yes, I just checked the NAS app and was informed that it uses SMB1 and SMB2. It is set to Switch between SMB2 and SMB1 automatically. No SMB3 appears to be offered.
Your link you sent is exactly what I did and tried to describe above.
BTW, I'm using Win 11 Pro on this machine, but the same problem occurs on Win 11 Home as well.

Should I disable SMB1 in the NAS? Just use SMB2?

 

[Ralston18]

SMB etc. can be problematic.

However, going back a step:

Were you able to check all of the networking requirements and configuration settings?

E.g.: network name, IP addresses, subnet masks, macs, login names, passwords, mappings etc...?

Verify that all are intact and otherwise correct.

 

[box o rocks]

SMB etc. can be problematic.

However, going back a step:

Were you able to check all of the networking requirements and configuration settings?

E.g.: network name, IP addresses, subnet masks, macs, login names, passwords, mappings etc...?

Verify that all are intact and otherwise correct.

I guess all those parameters must be correct. Why do I say that? Because suddenly I am able to access my NAS today! And I don't know why.
I turned on this 24H2 PC a few minutes ago and noticed my desktop icon for my share folder was no longer x'ed out. So I clicked on it and... there's my NAS. I can't remember if, during all my research and reading yesterday, I changed something or not. I didn't think so, but now I'm not so sure.

Well, I'm glad its working, but it's frustrating not to know why. Thank you.

 

[Ralston18]

Look in the logs -all that are available.

Also look in Relibility History/Monitor and Event Viewer.

Update History as well.

You may find some error code, warning, or even an informational event just before or at the time NAS access was lost.

Or when access re-appeared. Or both.

Check for restarts.

 

[box o rocks]

As near as I can tell, it had to do with disabling digital signing and allowing un-secure guests access. The last one is a mystery because I'm logged on to the NAS with my name and password. I shouldn't have to allow that last one. God, I miss W10.

Let me ask a follow up question; If I stay with 23H2, will Microsoft stop updating 23H2 now that 24H2 is out?

 

[Ralston18]

Good to know - thank you.

= == =

Regarding:

"If I stay with 23H2, will Microsoft stop updating 23H2 now that 24H2 is out?"

Not everyone is able to update to 24H2 so I would not expect Microsoft to completely stop updating 23H2.

At least not immediately.

Updates to 23H2 may be limited to critical requirements regarding security vulnerabilities, discovered bugs, etc..

Eventually, as has happened in the past with other updates, all support for 23H2 will end.

There may be other comments posted.

 

[box o rocks]

I'm a little concerned about enabling unsecured guests. If I can access my NAS w/o using my password, can't anybody?

 

[Ralston18]

What is meant by "unsecured guest"? I.e., "Everybody"?

You are not a guest.

You should be accessing the NAS as an admin or some other permitted user having the necessary login permissions.

The NAS can be/should be configurable to grant access to selected users/systems.

If the guest (?) is not included then the guest should not be given access to the NAS either in whole or in part.

Not (full disclosure) a Buffalo user.

My recommendation is to open a new post that directly asks about your questions and concerns regarding access rights to the Buffalo NAS.

Forum = Storage.

 

[HeyGro37]

So i think i figured out the issue, I ran into same problem today setting up a new laptop...... I have an older Buffalo NAS (at least it supports SMBv2)..... On Win11 24H2, the Buffalo NAS Navigator software would detect the NAS on my network, but i could not browse it or map any drives to it. Windows 11 24H2 introduced / changed some of the SMB security defaults requiring security signatures and insecure guest logins. If you open Powershell (run as Admin) and run the following two commands, you should be able to map your drives again..... at least it worked for me:

Set-SmbClientConfiguration -RequireSecuritySignature $false

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

The following Microsoft TechCommunity article is where I finally found the solution and a good explanation of what changed in 24H2:

Accessing a third-party NAS with SMB in Windows 11 24H2 may fail | Microsoft Community Hub​

Changes to SMB security in Windows 11 24H2 release preview may prevent access to third party NAS appliances or other devices.

techcommunity.microsoft.com

You'll obviously still need to make sure the right version of SMB is enabled for your NAS, I believe SMBv1 is disabled by default in Win11.

Hope this helps if it's still an issue for you.