Forum Discussion
Cannot access anonymous file shares after updating to Insider Preview 2004
The screen shot of my problem and specific build are attached. I updated my desktop pc to the Insider pre-release for Windows 10 2004 and now I cannot access anonymous file shares any more. Before the update, I enabled the option in the Local Group Policy at:
I ended wiping my PC clean and performing a clean reinstall of Windows 10. I'm not enrolling in the Insider program any more with potential bugs like that. I tried at least.
19 Replies
Tried your suggestion but didn't work.
I had it working for 1 day after updating to 2004 by changing group policy 'Enable insecure guest logons' to 'enabled'.
But after reboot, it no longer works. Tried the reg parameter fix you suggested as it didn't exist in registry, but still doesn't work.
Might be that the key is incomplete. Did you mean that you didn't have the key at all? Or just missing that value in the key?
I have this in my reg file for this:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"EnablePlainTextPassword"=dword:00000000
"EnableSecuritySignature"=dword:00000001
"RequireSecuritySignature"=dword:00000000
"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
77,00,6b,00,73,00,73,00,76,00,63,00,2e,00,64,00,6c,00,6c,00,00,00
"ServiceDllUnloadOnStop"=dword:00000001
"AllowInsecureGuestAuth"=dword:00000001
"SMB1NATCompatibilityLevel"=dword:00000001
I created an account just to say that i encountered this and found that the easiest solution was to go to my linux machines that were hosting the share and adding a user for smb using:
smbpasswd -a <usersname>then going into /etc/samba/smb.conf and adding these to the share:
guest ok = no valid users = <users you just added to smb>I then restarted samba with this command for debian:
systemctl restart smbd.servicethen in windows I added the shares using the user I added to samba and chose to remember the credentials. i asked my twice but i chose to remember credentials both times and it worked.
obviously this isn't a solution for if you WANT to use guest access, but this will stop making windows complain about it.
it seems that v2004 has changed behaviour for the policy 'Enable insecure guest logons' in Windows 10 Enterprise + Education editions...
Now even with that policy enabled it still throws event id 31017 in SMBClient logs
source of information (note the bit about enterprise and education editions)
https://support.microsoft.com/en-au/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser
happyshow, just wanted to add a +1 to this. I find myself in exactly the same situation as you. Linux SAMBA Shares at home with Guest access enabled. Upgraded my 1909 machine to the 2004 Insider Build and even though the Group Policy is properly enabled, it acts as though it was not.
I ended wiping my PC clean and performing a clean reinstall of Windows 10. I'm not enrolling in the Insider program any more with potential bugs like that. I tried at least.
happyshowJust thought I'd let you know I found the answer to this question. It appears that the Group Policy setting is not correctly modifying the Registry Entry it's supposed to be tied to. If you check this https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser it refers to the Registry Entry specifically. If you manually change that Registry Key, your Guest access will work again (doesn't even require a reboot). I'm guessing this is ultimately an issue with the GP templates which they will hopefully fix before final release.
- Is your network share another Win10 client or something else? Are you seeing anything in the event log? Also exactly which build are you hitting this on?
Eddie Leonard The share is from a Linux distro called Daphile where I store my personal music. For my current build information refer to my first post. FYI, stating again, my pc was updated to the insider preview 2004 and it doesn't work. I can access the share on my Mac and my Windows 10 laptop.
happyshow I apologize, I didn't look at the second screenshot to see the build number. Build is more important than version when tracking issues. Take a look at the Event viewer and see if there are any errors in the security or system logs.
Also can you please file feedback on this issue in the Feedback Hub? Be sure to use Files, Folders, and Online Storage > File sharing for the category. Then use Recreate my problem to walk through your steps. When done, please share the link with me, so I can take a look.
-Eddie
happyshow First I don't recommend enabling that policy from a security perspective. Second, is this a corporate/managed device or personal?
Third, do you know if your file share is setup to use SMBv1, v2, or v3? If v1, I recommend moving it to v3.
-Eddie
Eddie Leonard I understand the security implications. This is my personal network and devices not a corporate network. The share in question uses SMBv2 +. I do not use SMB v1 in my network.
