Forum Discussion

NPD_Johnny's avatar
NPD_Johnny
Copper Contributor
Mar 10, 2025
Solved

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 belie...
configuration
Features
Update management
  • YarrowSterling's avatar
    YarrowSterling
    Mar 11, 2025

    While the above steps might help in accessing your NAS by its name, if you still cannot access the NAS using its IP address, consider the following:

    1. IP Address Format: Make sure you are using the correct format. For example: 
    \\192.168.1.100\sharedFolder
    2. Firewall Settings: Check if Windows Firewall or any third-party firewall is blocking SMB traffic. You may need to create a rule to allow SMBv1.
    3. Check NAS Settings: Ensure that the NAS has correct network settings and that it's configured to accept connections over SMB.
    4. Firmware Update: Ensure that your NAS is running the latest firmware, which might improve compatibility with newer Windows versions.

QuincyWilder's avatar
QuincyWilder
Iron Contributor
Mar 11, 2025

Accessing older NAS devices using SMB after the Windows 11 24H2 update can be problematic, but you can resolve these issues by adjusting certain settings in the Windows Registry and Group Policy Editor. Start by navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters and setting AllowInsecureGuestAuth to 1; modify or create DWORD values for RequireSecuritySignature and EnableSecuritySignature both set to 0. Ensure the SMB Client feature is enabled via Windows Features and run the PowerShell command Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client -NoRestart.

Resources