By skyforbes I hope this post helps anyone facing the same or similar issues we encountered with Windows 11 24H2 and SMBv1. I understand that SMBv1 has many vulnerabilities; however, as we are in the process of migrating that file share to a new application, we need to ensure that access to the old share continues to work for archiving/historic purposes.
For several days, we investigated an issue where Windows 11 24H2 machines could no longer connect to the old file share via SMBv1. Downgrading them to 23H2 or earlier resolved the problem. We tried every command suggested online, but nothing worked.
-EnableInsecureGuestLogons $true
-RequireSecuritySignature $false
-EnableSMBQUIC $false
-DisabledSMBQUICServerExceptionList "IP address"
Also adjusting local Group Policy, enabling advanced sharing settings on the network adapter, enabling NetBIOS over TCP/IP—none of these resolved the issue.
In the end, since we couldn’t fix the problem through those methods, we went back to basics. As we were accessing the file share via IP address, we created a local DNS record in the hosts file to point to that IP.
Another thing we noticed on the firewall was that port 80 was blocked on the policy (while TCP ports 137, 138, 139 and UDP port 137 were enabled). Once we tried accessing the file share via DNS name instead of IP, and ensured port 80 was open, access started working again.