Windows 10 cannot access CIFS/SMB/Samba network shares
The official version of Windows 10 has been released for some time. Have you found that Windows 10 cannot access the CIFS share of FreeNAS normally? This article will tell you how to solve this problem.
fault repeat
In the Windows 10 network, the FreeNAS host can be seen.
Double-clicking the FreeNAS host pops up an error saying "\\freenas cannot be accessed. You may not have permission to use network resources. Please contact the administrator of this server to find out if you have access. This account is not logged in from this workstation. authorized"
crux of retrospect
The main reason for this problem is that the Windows 10 operating system wants to make your computer "more secure", thereby prohibiting you from accessing remote file servers anonymously. Microsoft's official explanation is this:
The security change is intended to address a weakness when using guest access. While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere. Without an account and password, the client doesn’t end up with a secure connection to the server. A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data. This is not necessarily a big concern in your home, but can be an issue when you take your laptop to your local coffee shop and someone there is lurking,ready to compromise your automatic connections to a server that you can’t verify. Or when your child goes back to the dorm at the university. The change we made removes the ability to connect to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation.
Solution
Microsoft recommends that you set up an authenticated share for your NAS server, or use a homegroup to share files. Here we would like to thank Microsoft for its concern, but we don't need it. It's our business to use anonymous sharing or not. We can take the risk ourselves. Please don't make it difficult for us.
Come on, friends, let's enable anonymous access to CIFS shares:
Step 1: Open the Registry Editor
Use the shortcut key (win + R) to open the run window and enter regedit.
Step 2: Locate the target
Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters in turn.
Step 3: Add a new value
Right-click Parameters and select New → DWORD (32-bit) Value from the pop-up menu
Step 4: Set the value
Create a new item named AllowInsecureGuestAuth and set the value of this item to 1 .
You can now access the CIFS anonymous share. If the system pops up a login dialog box, enter everyone or nobody for the user name, leave the password blank, and log in!