Accessing a third-party NAS with SMB in Windows 11 24H2 may fail (Work Around)

So as we all know that Windows 11 24H2 created an issue for us that have older NAS products and have been using it for years and the fact that they still work, points to this topic write.

I believe in to the point solutions without all the GIGO.

This fix is an attempt to restore the SMB settings back to what they were before the update 24H2.

One important thing here is that it allows me to access the OLD NAS by its network name address

Eg: /serverName/sharedFolder

But it did not allow me to access my NAS using its IP.. further research needed.

Good luck and here it is:

First if you are using a Windows Home edition, add the gpeditj (Policy Editor)

Put this inside a *.bat file and run in a command windows opened with admin rights.

add_gpedit.bat

===========

ech0 off 
pushd "%~dp0"
dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt 
dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt
for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"%SystemRoot%\servicing\Packages\%%i" 
pause

FIX SMB CONNECTION after 24H2 Update on Windows 11

In Registry:

Navigate:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

Look for:

AllowInsecureGuestAuth → If it exists, set it to 1. (If not, create a DWORD (32-bit) value and set it to 1.)

Find:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

Modify or add these registry entries:

RequireSecuritySignature: Set this to 0 (if it was set to 1).

EnableSecuritySignature: Set this to 0 (if it was set to 1).

Enable plain text password:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

If the value EnablePlainTextPassword exists, set it to 0 (or delete it)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Set RequireSecuritySignature to 0 if it was set previously.

In Windows Features:

Make sure SMB is on and uncheck the removal one

Only check the Cleint SMB

Then in Powershell:

Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client -NoRestart

gpedit.msc

Enable Guest Access for SMB2

Navigate:

Computer Configuration > Administrative Templates > Network > Lanman Workstation

Find:

Enable insecure guest logons

Enable it.

Navigate to:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

Look for the policy:

Microsoft network client: Send unencrypted password to third-party SMB servers

Make sure it is : Not Defined or Disabled if it exists.

Default SMB setting:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

Find these two policies and set both to "Not Configured" or "Disabled" (depending on the previous state):

1. Microsoft network client: Digitally sign communications (always)
2. Microsoft network server: Digitally sign communications (always)

Also check if these are enabled:

Microsoft network client: Digitally sign communications (if server agrees) Disabled

Microsoft network server: Digitally sign communications (if client agrees) Enabled

Then Apply then OK

secpol.msc

Navigate:

Security Settings > Local Policies > Security Options

Find:

Network security: LAN Manager authentication level

Set it to:

Send LM & NTLM - use NTLMv2 session security if negotiated

On the TCP/IPv4:

Enable NetBIOS over TCP/IP under properties

Update NFS Mapping in Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default

Add or modify these DWORD values:

AnonymousUid = 0

AnonymousGid = 0

NOT REALLY NEEDED BUT HELPFUL

wsl --install -d Ubuntu