In Build 9926 of Windows 10 Microsoft removed the ability to connect to unsecured network shares by default. For me and many others this includes Samba and NAS devices. Fortunately, you can enable the ability to connect to these shares by editing the registry.
The short version: add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth key, value set to 1.
The long version:
Click the Start Menu and type in regedit.
Right click the regedit command and choose Run as Administrator.
Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters key.
Right click the contents pane and choose new DWORD (32 bit value).
Name the new key AllowInsecureGuestAuth.
Double click the new value and change the value to 1.
Close regedit and you should now be able to access unsecured network shares.
EDIT
Microsoft is correct in that the better way to handle this is to protect your shares with authentication, and to use said authentication when connecting to the network resource in question. However, it’s not often that a computer sits in a void by itself. If I were to password protect these shares there are multiple processes I’ve created which would have to be updated. Legacy systems in the home, as it is.
You are a Legend.. This worked for me. Thanks
Hello.
I came here searching a solution for this problem I found after update to Windows 10.
Initially this solved my problem, after I added the new line in registry, I rebooted the computer and ok: I can access to the shared folders in my NAS.
But…. the problem reoccurs every time the pc go into sleep mode or even only when the screen turns off.
When this occurs only a reboot solve again the problem… until the pc go into sleep mode again.
What could be the problem??
Thanks.
Do you have any antivirus or software which would be monitoring and restoring changes to your registry? When the PC reawakens or reverts to the previous behavior, has the registry change reverted?
You could run SysInternals ProcessMonitor and see what process is being triggered that’s editing the key.
Hi bmschkerke.
As antivirus I use Kaspersky. Really I don’t know if it is monitoring changes in the registry.
But the registry doesn’t change. Since I have created the new key AllowInsecureGuestAuth and change its value to 1 this value was always 1. After PC reawakens the value of AllowInsecureGuestAuth continues being 1. But, I can’t access to the shared folders of my NAS.
To solve temporaly the problem the only thing I have to do is reboot the PC. I don’t need change anything in the registry. Then the shared folders are again availables….. until the PC goes to sleep again.
Regards.
First, I’m going to freely admit I don’t know what’s going on. But I have a few questions that might spark a drive in the right direction, if you haven’t investigated them.
1. Could it be related to your wireless network? Are other networks (the Internet) or network shares available when the NAS shares are not? Can you ping the NAS by device name or IP when the shares are unavailable?
2. Have you tried removing the permission to disable your network card for power management? (Device Manager -> Network Adapters -> Properties of NIC -> Power Management Tab -> uncheck “Allow the computer to turn off this device to save power.”
3. Have you checked for newer drives for your network card? WindowsUpdate doesn’t always deliver the latest and greatest.
4. For a similar problem in Windows 7 it was recommended to try disabling the HomeGroup. Stop the HomeGroup Listener and HomeGroup Provider services to do this in Windows 10.
5. Is the NAS compatible with IPv6? Perhaps try disabling IPv6. View Network Connections -> properties of network adapter -> uncheck “Internet Protocol Version 6 (TCP/IPv6).”
6. Another tip I saw related to Windows 7 but perhaps still applicable: are you using hybrid sleep, sleep, or hibernate in your power settings? Try switching it to an alternate.
7. Finally, is there a way to turn on Samba debugging on the NAS? It’d be nice to compare the successful login process and the post sleep failed login process.
Unfortunately the most common response appeared to be “it’s a device driver issue, not Windows, and you should just turn off sleep mode.”
Thanks.
Hi.
Thanks for your help. Unfortunately nothing of that have solved my problem.
I’m going to investigate the other hand: the NAS. My problems began coinciding in time two events: the update to Windows 10 and the update of firmware of my NAS. So perhaps there is some problem with the NAS.
Strange things are happening in my network:
-I can access without problem to the shared folders of the NAS from my Android phone.
-But I can’t access to the shared folders of my PC from the same Android phone, when before I accesed it without problem.
-I have also an Android “top-box”, and using XBMC I can’t add as source any shared folder through SMB (I get the error: “error 2: resource unavailable”).
It should be able to access both the NAS and the PC.
However I can access to the previous folders I had added as source (SMB) and I can access all the shared folders through AFP protocol (these only in NAS).
It is also curious that before upgrading to Windows 10 my PC wasn’t go to sleep at the scheduled time (for some reason I couldn’t find), just pressing the power button. Now it’s going to sleep ok … but I have other problems…..
Regards.
I tried this to no avail. I upgrade my home computers to Win10. From my phone using ‘ES File Explorer’ I can get into the drive I have shared on my desktop computer. When I try from the laptops, including after adding this registry key I get an “Windows Cannot Access … You don’t have permissions”. I do anonymous access from my Android phone. Opening File Explorer, going to Network, the computer is there, I can open it to see the share folders, but when I open them it is just permission errors.
Any Ideas? Did I miss something?
Finally …
I have put many hours to reach my NAS after upgrading to Windows 10!
Now it works!!!
Many thanks!
/ Hook
did not help me as son as i click the samba computer this login appears i tryed all my usernames including root no ones entering the samba from win 10 on a win 7 or a linuxlite all users works!
i have tried the above and still not working. i keep getting this box poping up when trying to connect to a usb drive that is on my windows box. Prior to upgrading to windows 10 this worked flawlessly.
[IMG]http://i64.tinypic.com/2lc0ak6.png[/IMG]
http://i64.tinypic.com/2lc0ak6.png
Ben,
That image is tiny. Any way to get a larger resolution? You might try http://www.imgur.com for image hosting as well.
Thanks.
Brian
SOLVED! I had a similar problem connecting Windows 10 to an older NAS. Here is my solution:
There is a setting in windows Local Security Policy which is incorrectly set by default for viewing an older communication protocol NAS.
To access said setting go to the control panel in Windows 10 (or 7), in Category view click on the text “System and Security”, then click on the text “Administrative Tools”.
Now double click and open “Local Security Policy”.
In the Local Security Policy screen on the left navigation tree, expand the “Local Policies –> Security Options” then about 2/3rd’s the way down the list you’ll see a Policy called “Network Security: LAN Manager authentication level”. Double click and change the setting to be “Send LM & NTLM – use NTLMv2 session security if negotiated.”
Then just press OK and close all of the open windows and then try again
In the case of Windows 10 Home, Local Security Policy does not exist; therefore make the change in the registry (use regedit).
HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\LSA
Add:
LMCompatibilityLevel
Value Type: REG_DWORD – Number (32 bit, hexadecimal)
Valid Range 0-5
Default: 0, Set to 1 (Use NTLMv2 session security if negotiated)
Description: This parameter specifies the type of authentication to be used.
Dan – Your the man! I have been searching for a resolution to my issue with connecting to a NAS since upgrading to Windows 10. Your process worked perfectly. Thanks a million.
Thanks, that fixed it for me too.
SUUUPER !! It really works!
Thanks a lot.
This fixed it for me, wasted about 5 hours but this works! yeay! thanks a lot
Thanks Dan! I searched all day for a solution and ran across this. Your instructions worked perfectly for both my windows 7 machine and the regedit for my windows 10 home edition machine. I was getting “device not set up to accept connections on port the file and printer SMB” when trying to connect to a 2 TB drive on a Linksys AC1750 router. Finally I can access the 2 TB drive! thanks so much for the post, even though post was almost 2 years ago solution still works.
Dan,
Spent three hours examining Samba.conf, using the Regedit key like you said same issue did not allow.
Then I did what you suggested here it worked..Your a star, thank you.
Dave
Dan,
many thanks from Germany. All of a sudden, my Raspi Samba did not appear on my Win10 laptop. Your workaround has finally been the solution. Thank you for this!
Dan,
Thanks for this fix for SMB acccess on my 11 year old Redhat Linux filestore box.
Client is a Windows 10 Home, build 10586.36 laptop.
Had been searching for a soultion for a while, so this is great.
Worth noting that my problem was that SMB client was running on the laptop and could see the server, just that connection using a valid login was not possible.
Had kept things going with file access using WinSCP in the mean time, but that was not really a long term solution. This is.
Regards and thanks again
Dan, Help. I’ve tried the Regedit fix to no avail. Allow me to explain. I have multiple win10-home computers in the house & 2 Nas drives, all on the same network. Windows explorer shows connected computers but used to include my 2 NAS drives as well as my NUS drive. As of yesterday, only the computers show. However my “KODI” media player (on my laptop and others) still allows me to view media already stored on these drives. I can not move file to and from these NAS drives.
It works, but the device isn’t shown in the Network explorer, you have to enter the name manually in the address bar: “\\HOSTNAME”
This fix did not address my unique situation. With Win 7 Home I logged into a Mac 10.8.5 server without any problems using username and password. After Win 10 upgrade, the username/pwd prompt comes up, but won’t connect to the Mac server using same username and pwd. It does however, connect if I use the Mac’s admin username and pwd. Of course this is just for testing, I can’t really use that normally. I updated Win 10 home to Pro and set SecPol to NTLM2, but still nothing. I implemented your Registry suggestion – still nothing. Any thoughts?
[…] Si vous utilisez Samba pour partager vos fichiers et que vous souhaitez y accéder depuis Windows 10, par défaut ça ne fonctionnera pas en effet Microsoft a désactivé la possibilité de se connecter à un partage non sécurisé par défaut. […]
This was not solving my issue with windows 10 workstation, the problem is, that I cannot connect to my SAMBA fileshare, it is working from other clients and I can ping and connect with FTP.
When I diagnose, windows replies “protocol is missing”
So I try to add the service
C:\WINDOWS\system32>sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
[SC] ChangeServiceConfig SUCCESS
But it did not install:
C:\WINDOWS\system32>sc.exe config mrxsmb10 start= auto
[SC] OpenService FAILED 1060:
The specified service does not exist as an installed service.
And when checking the Service:
Command line ” SC.EXE QC mrxsmb10″ replies:
The specified service does not exist as an installed service
When checking the files, I have the files:
Directory of C:\Windows\System32\drivers
30-10-2015 08:17 430.944 mrxsmb.sys
30-10-2015 08:18 285.696 mrxsmb10.sys
30-10-2015 08:17 216.408 mrxsmb20.sys
I assume one fix could be to reinstall SMB protocol? how do I get an install image? can i get only the SMB part from Windows
Any idea how to fix the issue?
I would definitely start with reinstalling File and Printer Sharing for Microsoft Networks. Other than TCP/IP (v4 or v6) that’s the only pre-requisite I’m aware of for Windows to use SMB.
You can download an install image from https://www.microsoft.com/en-us/software-download/windows10. It will let you download an ISO or install it directly to a thumb drive if you have one available.
Thanks. I works.
After struggling for hours, I found your post. It worked for me, thanks alot!
It should be noted that you need to restart the Workstation service after creating or changing AllowInsecureGuestAuth. You can do this in services.msc, or simply reboot.
In file “/etc/samba/smb.conf”, just add this line:
ntlm auth = yes
Yes! You are a legend! It’s worked for me too!
Thanks, lost connection after updating to Windows 10 creators update. After many hrs, this was the only fix that worked!
I made it too, but with different solution: I had to define in my NAS:
1) share folder
2) users wit access
3) group for users, also with access for group (read, or read/write)
I didn´t make 3rd step at first, so my windows had problems with that NAS (connection refused). Now after setting 3rd point everything works without changing the registry.
Like others have said, you are The Man (or insert your gender agnostic awesomism of choice) for documenting this.
This ended up being the magic bullet for me – for some reason this only hit me when I updated from win10 1703 to 1709. Drove me nuts for 2 days when couldn’t access any shares on my win7 and 8.1 machines FROM 2 win10 boxen (any attempt to access those machines it like those machines don’t exist), and accessing a 3rd win10 box still on 1703 (FROM a 1709 box) it started asking for username/password for shares that had none.
What will really drive you nuts is that all of the win7 and 8.1 machines could see shares on the win10 boxen fine. Everyone can see you, but you can’t see anyone. Makes sense now knowing the answer, but ugh asymmetric.
That 3rd Win10 box I have that’s still 1703 doesn’t even have the key (AllowInsecureGuestAuth) so I’m pretty sure 1709 explicitly added it set to “0” on the other two machines.
All 3 machines are upgraded from win7 enterprise (actually 3rd was from 8.1, but same). I only mention enterprise as I thought I read somewhere they are flipping some of the network paranoia settings first for it vs other SKUs? I guess 1709 finally “enforced” the AllowInsecureGuestAuth setting even on upgraded win10ent installs? I’m guessing an upgrade win10 install keeps old settings + SMB1.0 by default, where a clean install of win10 would not.
This worked great! Thanks you are the dah man!
I have set the registry key and the Local Security Policy and I still get a password prompt. From what I read elsewhere, Microsoft broke it for good starting with the Anniversary Update (build 1607).