StrandedPirate Posted January 27, 2019 Share Posted January 27, 2019 (edited) Tons of posts related to Windows 10 and SMB as the root cause of the inability to connect to unRaid that were fruitless so I'm recording this easy fix for my future self. If you cannot access your unRaid shares via DNS name ( \\tower ) and/or via ip address ( \\192.168.x.y ) then try this. These steps do NOT require you to enable SMB 1.0; which is insecure. Directions: Press the Windows key + R shortcut to open the Run command window. Type in gpedit.msc and press OK. Select Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation and double click Enable insecure guest logons and set it to Enabled. Now attempt to access \\tower Related Errors: Windows cannot access \\tower Windows cannot access \\192.168.1.102 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network. Edited January 27, 2019 by StrandedPirate 23 19 Quote Link to comment
PiZZaMaN Posted January 27, 2019 Share Posted January 27, 2019 I LOVE YOU!!! <3 I have spend many hours to try to fix this including reinstall networkcard. I was sure something in unraid blocked me so i have uninstalled some plugings and changed some settings but no luck. And you just posted this one hour ago...its my lucky day =) 2 1 Quote Link to comment
Frank1940 Posted January 27, 2019 Share Posted January 27, 2019 @StrandedPirate, What variety (Home, Pro, ...) version of Win10 (1803, 1809, ...) did you find this a solution worked on? @PiZZaMaN, A reply from you would be helpful also! Quote Link to comment
StrandedPirate Posted January 27, 2019 Author Share Posted January 27, 2019 This has been confirmed to work on Windows 10 Enterprise and Windows 10 Pro both versioned as 1803. 1 Quote Link to comment
PiZZaMaN Posted January 27, 2019 Share Posted January 27, 2019 2 hours ago, Frank1940 said: @StrandedPirate, What variety (Home, Pro, ...) version of Win10 (1803, 1809, ...) did you find this a solution worked on? @PiZZaMaN, A reply from you would be helpful also! It worked on my system. Just checked and pulseway software reporting Windows 10 Enterprise 10.0.17134.0 1 Quote Link to comment
srandolph Posted January 28, 2019 Share Posted January 28, 2019 If as you try to access unsecure unRAID, you see this panel, insert \ backslash for user ID and click OK, your in. 13 4 2 Quote Link to comment
CBMX Posted September 21, 2019 Share Posted September 21, 2019 Dude, you are my hero. thanks a lot! Quote Link to comment
almulder Posted September 25, 2019 Share Posted September 25, 2019 Thanks so much, Tried a few dozen other things and nothing worked. This did right away. Thanks a million. Quote Link to comment
josywong Posted November 6, 2019 Share Posted November 6, 2019 my hero! thanks. Quote Link to comment
radwimp Posted November 6, 2019 Share Posted November 6, 2019 This worked for me, had no issues on 1809 but I had to update to the latest Windows version and ran into this issue. Thanks. Quote Link to comment
clambert Posted December 1, 2019 Share Posted December 1, 2019 So I am getting the Error Code 0x80004005 on Windows 10 Build 18362. Enabling this value doesn't seem to work for me. Are there any other known tricks? Quote Link to comment
Frank1940 Posted December 1, 2019 Share Posted December 1, 2019 4 hours ago, clambert said: Enabling this value doesn't seem to work for me. Exactly what have you tried? Have you watch this tutorial: https://forums.unraid.net/topic/53172-windows-issues-with-unraid/page/4/?tab=comments#comment-741282 Have you gone through this thread (start with page 6 and work backwards)? https://forums.unraid.net/topic/53172-windows-issues-with-unraid/ I am also assuming that you are trying to access shares when you get this message. Are your shares Public, Secure or Private? Fixing windows 10 SMB issues has been a nightmare. MS has continuing tighten security over the past few years. (I personally just had one crop up in the past month where they changed "Password Protected sharing" from 'off' to 'on' on the upgrade from 1809 to 1903 which meant I could not get to the shares on another WIN10 computer! But I still had access to my Unraid server...) Quote Link to comment
clambert Posted December 2, 2019 Share Posted December 2, 2019 3 hours ago, Frank1940 said: Exactly what have you tried? Have you watch this tutorial: https://forums.unraid.net/topic/53172-windows-issues-with-unraid/page/4/?tab=comments#comment-741282 Have you gone through this thread (start with page 6 and work backwards)? https://forums.unraid.net/topic/53172-windows-issues-with-unraid/ I am also assuming that you are trying to access shares when you get this message. Are your shares Public, Secure or Private? Fixing windows 10 SMB issues has been a nightmare. MS has continuing tighten security over the past few years. (I personally just had one crop up in the past month where they changed "Password Protected sharing" from 'off' to 'on' on the upgrade from 1809 to 1903 which meant I could not get to the shares on another WIN10 computer! But I still had access to my Unraid server...) So yeah, I did get it working by watching that video. I guess I was a little confused because I thought the thread mentioned being able to do it without enabling SMB 1. In the video SI One has us enable it. That's what I have done for now. It's fine I guess. Thanks for the help. Quote Link to comment
Typhoon Posted December 11, 2019 Share Posted December 11, 2019 Apologies for the old thread revival, but I wanted to say thanks for this workaround. I built a new Windows 10 gaming PC and was pulling my hair out as all my other devices (around 20-25 different systems) could all access my UnRaid servers fine, but this new gaming PC could not. Tried your workaround, as well as (reluctantly) enabling SMB1.0 in the Windows Features section, and it worked. Thanks again! Quote Link to comment
moralrelativity Posted March 1, 2020 Share Posted March 1, 2020 Thanks for the tip. Works on Win 10 Pro 1909. Quote Link to comment
pasgener Posted March 1, 2020 Share Posted March 1, 2020 On 1/27/2019 at 2:07 PM, StrandedPirate said: Tons of posts related to Windows 10 and SMB as the root cause of the inability to connect to unRaid that were fruitless so I'm recording this easy fix for my future self. If you cannot access your unRaid shares via DNS name ( \\tower ) and/or via ip address ( \\192.168.x.y ) then try this. These steps do NOT require you to enable SMB 1.0; which is insecure. Directions: Press the Windows key + R shortcut to open the Run command window. Type in gpedit.msc and press OK. Select Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation and double click Enable insecure guest logons and set it to Enabled. Now attempt to access \\tower Related Errors: Windows cannot access \\tower Windows cannot access \\192.168.1.102 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network. Thank you! Your suggested change to the gpedit policy fixed the inability of one of my Win10 PCs to access unraid shares after an OS reinstall (Win 10 Home 1909). Quote Link to comment
garethsnaim Posted March 1, 2020 Share Posted March 1, 2020 Well all I know is FreeNas and OpenMediaVault simply do not exhibit the same SMB issues that unraid does, it would be super cool if the developers spent some time actually fixing this issue, rather than constantly blaming windows. It might be windows for all I know, but other solutions work flawlessly, but I paid for unraid, so am somewhat stuck with none of my windows machines reliably and consistently connecting to my unraid server. The back slash thing works but it does not stick for me for such things as mapping network drives or for other apps to access unraid, that should be able to do so as guest. I'll give this solution a shot, but I honestly don't think I should have to be tinkering like this. 2 Quote Link to comment
NotMrSavvy Posted March 9, 2020 Share Posted March 9, 2020 Hi, I'm a new UnRAID user running a mixed macOS/Windows environment, and I was running into this exact issue on my Windows 10 machines. This is sort of my first question about UnRAID, (and almost definitely not the last,) but from what I can tell, it looks like I'm trading one security vulnerability for another with this solution. On 1/27/2019 at 2:07 PM, StrandedPirate said: These steps do NOT require you to enable SMB 1.0; which is insecure. This is good, as it's exactly what I wanted to avoid from Spaceinvader One's awesome videos as a result of security concerns. Naturally, I was thrilled when I first saw this thread, until I saw this wording in step three: On 1/27/2019 at 2:07 PM, StrandedPirate said: Enable insecure guest logons If I'm enabling insecure guest logons, doesn't that mean I'm potentially opening my network up to additional security vulnerabilities? If so, what are the advantages of using this method over enabling SMB1? Are their any advantages of enabling SMB1 over using this method to make my UnRAID server visible to Windows 10? Any assistance is greatly appreciated. Quote Link to comment
Frank1940 Posted March 9, 2020 Share Posted March 9, 2020 43 minutes ago, NotMrSavvy said: If I'm enabling insecure guest logons As I recall, the problem is that unless you allow this, you can not see any SMB shares on an Unraid server unless you first log onto that server as a valid user. (By extension, you can not see any Public shares on any Windows computer either. ) Now this is a great policy if you are using the 'free' WiFi at the nearest coffee shop but in a home environment, it can be more of a problem of than a security feature. Do you trust the people who you are permitting on your home network? In a business environment, trust is a much more complicated issue. There is more often a need-to-know basis issue and you do want to make sure that people can only see what they are suppose to see. Now, I have my Unraid shares on my home network set to 'Secure' which means that 'Guests' have only read privileges. And I don't have a user assigned to any share so basically no one can write, modify or delete and file using SMB! (I actually did this to prevent ramsonware from doing its thing if my network were to be compromised-- more likely someone does something really stupid.) Only you can define the what and why of your security problem. You have to start by asking who and why would someone be attempting to get at your data. And, if they succeed, what will they be doing with it. If you are trying to hide something from some three-letter government agency somewhere in the world, you are far beyond the skill set of any of us. Quote Link to comment
NotMrSavvy Posted March 9, 2020 Share Posted March 9, 2020 Thank you for your help Frank1940. For this particular array, I'm indeed in a business environment, and while the array is reasonably secure, my main concern is with keeping it that way, especially if one of our systems that connects to the array were to ever unknowingly be compromised in some way. Quote Link to comment
Frank1940 Posted March 9, 2020 Share Posted March 9, 2020 I am not qualified to advise you at the point. You could map each share (as a drive) that the user for each computer has the need to access. I don't think, the WIN10 computer needs to be able to see the share to do this. Of course, MS does have tools to help the system admin do this sort of thing (as I understand it). Quote Link to comment
ReVRiN Posted April 10, 2020 Share Posted April 10, 2020 My primary gaming system shit the bed and I was unable to even hit the server post rebuild. Thank you for the instructions. My brain is on overload these last few weeks and I couldn't for the life of me fix my own system, yet I keep my firm's network running like clockwork. Ironic. Stay safe everyone, and stay the fuck home. Quote Link to comment
Zonediver Posted April 11, 2020 Share Posted April 11, 2020 (edited) Using Win 10 Pro 1909 and all is working fine. What i did, was different. On unraid under "Settings", "SMB", "SMB-Extras", "Samba extra configuration:" i implemented the following: min protocol = SMB2 Can access my unraid-shares from every Win10 Comp on the network. Edited April 11, 2020 by Zonediver 2 1 Quote Link to comment
Mazzic518 Posted April 20, 2020 Share Posted April 20, 2020 Thank you. I actually registered an account here just so I could thank you, been pulling my hair out wondering why my shares suddenly stopped working and this fixed it. Quote Link to comment
SZ68 Posted April 27, 2020 Share Posted April 27, 2020 I am new to Unraid and coming from Freenas. I had my unraid SMB share working fine from my Linux PCs and my Windows 10. Now all of a sudden it stopped working from Windows 10. It may have been the latest 10 update. I am now running 19041.207 from my Win 10 desktop and laptop. I can't reach the Unraid SMB share. I tried clearing the credentials Windows had save for my unraid server and I have the Lanman workstation setting to allow insecure. Any ideas what else I can look for since it was working before? Thanks Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.