You can’t access this shared folder because your organization’s security policies block unauthenticated guest access

Aruna Fernando

March 2, 2018 167

You can’t access this shared folder because your organization’s security policies block unauthenticated guest access

I ran in to this while I was trying to access My Lacie NAS drive from my Windows 10 computer. NAS was directly connected to the network and no access permissions required to access the shared folders. I have set permissions according to the user groups. So anyone who got the access permissions can access the relevant folders and if users don’t have the permissions folders will not be displaying in the explorer.

So I tried to connect this drive as a Network file share to my laptop and I was prompted with this error message on my screen. So I thought to share this post in my blog so anyone who has the same issue able to find this in the internet easily.

This is the prompted error message

So I found that this access is blocking from the local group policy and I opened the Run window (Win + R) and typed gpedit.msc to open the Local Group Policy Editor.

Navigated to Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation and selected the Enable insecure guest logons as shown in the below screenshot

By default it was disabled and I have enabled the policy

Click OK to apply the policy and tried to access the shared network drive, I was able to access My Lacie NAS drive from the windows explorer

If you found this post as useful please rate the post and share it!

Click to rate this post!

[Total: 399 Average: 4.9]

167 responses

Abdul Ahad

Thanks, I got it very useful.

Reply
1. krishnakanth
  
  yaa it is so usefull
  
  Reply
sicoyy76

tks for you info

Reply
kameshwar prasad yadav

thanks it is very useful information.

Reply
Nadun Sirimevan

Thanks it was really helpful. Keep up the good work..

Reply
bora nong

Thank it’s very helpful..

Reply
chris

Continue the good work. Really helps me out. Thank you.

Reply
behzad

thanks it was really helpful.

Reply
Md. Abdul Bari

tnx working

Reply
edward

what’s the fix for Win 10 home?

Reply
1. Aruna Lakmal
  
  Windows 10 home doesn’t have a gpedit.msc console. You have to install it manually as a third party tool. There are many links available in the internet. After installing the tool just follow the steps. Hope this will help you out. Thanks for the comment.
  
  Reply
  1. ALAN WALSMITH
    
    does this fix need to be done to my pc or the pc im trying to conect to
    
    Reply
    1. Aruna Lakmal
      
      This should be in your local machine!
      
      Reply
2. Andrew Fox
  
  Open Regedit, navigate here:
  
  Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
  
  Double click on AllowInsecureGuestAuth and change it from 0 to 1. It should instantly start working without having to restart the computer or any Windows services/processes.
  
  Reply
  1. Aruna Lakmal
    
    Thanks Andrew for your input.
    
    Reply
sripati muduli

thanks it work…………….

Reply
Yoshiaki Gomes

Many thanks Mr. Aruna.
It’s Working perfectly.

Reply
deli0870o

work solve my problem bu don’t forget to set Computer Configuration->Windows Settings->Security Settings->Local Policies->Security Options
set Microsoft network client: Digitally sign communications (always) -> Disabled

if you done so

Reply
1. D
  
  Thats for that. This was the REAL fix.
  
  Reply
jan paul

SO MUCH THANKS MATE!

Reply
Tracey

You saved the day. Thank You so much. I tried everything. I wish I would have found this last week.

Reply
sahil shaikh

it is useful

Reply
siva

It is very useful.Thanks

Reply
bc

works! Thanks.

Reply
sridharan

thanks bro….

Reply
Bahaeldin assad

it’s works thank you a lot

Reply
Steve

Thanks ! After long trials this was the solution.

Reply
dollygene palattao

it works, thank you!

Reply
Munusamy

Awesome!!!!!!!!!!!!
It’s Works

Reply
Joshuaedwardk

Thank you sir, you are a you hero for today

Reply
Chetan

Awesome!!!!!!!!!!!!
It’s Works

Reply
RITESH VISHWAKARMA

thanks …….

Reply
LibbyLA

Thank you! My new Surface Go was talking to my desktop computer beautifully last week, then this week the two refused to communicate. I tried all the usual troubleshooting steps and even created a new workgroup. My two older Surfaces and the desktop worked together and the Go would talk to the Surfaces, but I couldn’t get the Go and desktop working together.

Fortunately, this morning, I got the error message you wrote about, searched for info on it, and your instructions helped me fix the problem. Count me as another very relieved reader of this blog entry.

Reply
1. Aruna Lakmal
  
  LibbyLa, Thank you very much for your thoughts!
  
  Reply
Labib

Thanks for your Help…
It was a Great pleasure for me…

Reply
rahul yadav

Thank you it work like a charm 🙂

Reply
toko gigi mutiara

Thx bro, it’s work

Reply
PRITAM GHOSH

thx a lot

Reply
www.zaidan.com

bravo… you just save my day mate…

Reply
haitham

Thank you so much

Reply
rami

it works perfectly. thanks
a point to notice, i dont play with any local policy so i think its happened during one of the windows updates

Reply
Izaz

Thanks this is helped me

Reply
Dan

Thank you very much. This doesn’t have with all versions of Win 10. I came across it with Win 10 Enterprise when I was trying to access my SAMBA share on Linux.

Thanks again.

Reply
infotechnab

Thanks It works.

Reply
itmanag

Thanks a lot

Reply
poring

dude you rox! keep it up. thank you

Reply
Nikolay

thanks! helpful no more problem)

Reply
Hosni Wijaya

Thank you a lot very much, After almost 1 year, finally I can access my shared folder and shared printer again, because of this article. This unable to access the shared folder has already annoyed me since Win 10 patch 1803.

Reply
tealcuk

Thanks so much. Finally found something that actually fixes this problem

Reply
1. Aruna Lakmal
  
  Glad to hear that I was able to help!
  
  Reply
saad

thanks

Reply
1. Aruna Lakmal
  
  Your’e Welcome!
  
  Reply
zz

TQVM!

Reply
1. Aruna Lakmal
  
  (thumbsup)!
  
  Reply
jasonmcallister

In Windows 10 Pro, was able to use your instructions as written to fix the same error on a netgear readyshare device that refused to connect. Worked immediately after following your steps. My sanity is now restored.

Reply
Eduardo Villegas

Thank you! I was struggling on how to fix this, happened to me since couple days ago when I factory reset my laptop. Thanks again sir! 🙂

Reply
Ian

Thank You Aruna. The perfect solution after days of frustration with Windows 10 build 1809. Even though the default setting was “not configured”, I did not have network access to my other workstations. Fixed immediately with the “enabled” setting.

Reply
Miroslav Papic

OOOOO Finally I got full network. Almost 1year I am looking for solution. I have 2 WIN 10 PC and can not share printers and folders. I test all solutions, all pc are updated to last version. Only this security changing allow me to full share printers and folders. Thank you for good solution.

Reply
hhhhhhhhh

Thank you

Reply
Layne Royer

I LOVE YOU (no I’m not gay). Spent days updating, reconfiguring, resetting. Cause only one PC on the network was being stubborn and couldn’t browse said network. No idea why this was necessary but definitely solved my problem and in literally 2 mins. Thanks a million.

Reply
1. Aruna Lakmal
  
  Ha ha nice comment! 🙂 Thank you for the complement and glad to hear that it resolved your problem.
  
  Reply
Vrushabh

I still get the same error

Reply
1. Aruna Lakmal
  
  This is the first time I heard this fix not worked, could you check again?. I’m not sure where there is any change from the Microsoft side. Did anyone experience this?
  
  Reply
Chinmay Rajyaguru (@chinmay691990)

Thank you so much man!

Reply
1. Aruna Lakmal
  
  You are welcome! Thanks for the reply!
  
  Reply
David

This worked for me!! trying for long time to access my WMMyCoud under Windows 10 Pro, with no success. Thank you!

Reply
1. Aruna Lakmal
  
  Thank you David for your reply!
  
  Reply
ceppy hasan basri

you help me. now i can access shared folder on my network

Reply
1. Aruna Lakmal
  
  Glad to hear that I was able to help you. Thank you very much for the comment!
  
  Reply
Teresa

Thanks that worked like a dream!!

Reply
1. Aruna Lakmal
  
  Thank You very much for the comment!
  
  Reply
codywarmbo64

Very helpful article. But I’m curious why this solution is needed? What triggers a logon as ‘guest insecure’? I’ve had no issues for years with this Server 2016/10Pro combo I’m using until last night! Patch Tuesday got me I guess.

Reply
1. Aruna Lakmal
  
  Thank you very much for your comment!
  Good question that’s something we need to ask from Microsoft 🙂
  
  Reply
EHB Enterprises and Printhaus

thanks you so much … you solved my problem

Reply
1. Aruna Lakmal
  
  You’re almost welcome… Glad to hear that I was able to help.
  
  Reply
Rehansyah

Thank you for solutions !!

Reply
1. Aruna Lakmal
  
  Happy to help!
  
  Reply
Kishore

Thank you

Reply
1. Aruna Lakmal
  
  Hi Kishore
  
  Thank you for your comment!
  
  Reply
David

After hours of struggling with a simple access issue this article was a godsend. Thank you!!

Reply
1. Aruna Lakmal
  
  That’s great! Thank you very much for your kind words David!😊
  
  Reply
IT SMKTLS

thanks, already tried other solution but none is working except this one

Reply
Nimmish

You made my day bro.

Reply
1. Aruna Lakmal
  
  Glad to hear that 🙂
  
  Reply
MB

Was having this exact issue on a windows 10 pro machine. This fixed my problem. Thank you so much!

Reply
1. Aruna Lakmal
  
  You are almost Welcome!
  
  Reply
Sanjeev Kumar Tudu

Thank you so much … 🤓 it worked.

Reply
1. Aruna Lakmal
  
  Glad to hear that Sanjeev!
  
  Reply
bala

Good job,It’s Work for me.

Reply
1. Aruna Lakmal
  
  Thank you for your comment and glad to hear that it worked for you!
  
  Reply
EEE Ron

100% WORKING ON MY WINDOWS 10

Reply
1. Aruna Lakmal
  
  Glad to hear that! Thanks for the reply!
  
  Reply
Chi Master

Life Saver!!! Been watching vids and enabling services and changing settings for days. The Lanman policy did the trick. Thanks a million! !

Reply
1. Aruna Lakmal
  
  Thanks Chi! Fo your Kind words! Glad to hear that was resolved with this.
  
  Reply
test piolot

thankk you

Reply
David Valdi

Works like charm. Good job on spotting the issue.

Reply
1. Aruna Lakmal
  
  Hi David
  
  Glad to hear that! 😊
  
  Reply
Lasse Langeland

Great, at least one solution to this problem, I have tryed all the others, This one WORKS.
Thank you !!!

Reply
1. Aruna Lakmal
  
  Hi Lasse
  
  Glad to heat that it was resolved! Thanks for the comment!
  
  Reply
Tim Higgins

Awesome I spent like 8 hours on this wiresharking smbstatus from the linux server etc. Nice easy fix

Reply
1. Aruna Lakmal
  
  Wow! Nice to hear that. Thanks for the comment!
  
  Reply
Job Okanga

Awesome, it works thanks man.

Reply
1. Aruna Lakmal
  
  Hi Job, Nice to hear that!
  
  Reply
Charan

Yes, it worked…. Thanks a ton

Reply
Ryan Cameron

Thank you so much !

Reply
1. Aruna Lakmal
  
  Anytime! 🙂
  
  Reply
Suyong Eo

Thank you! I’ve solved in WD MBL.

Reply
1. Aruna Lakmal
  
  Hi Suyong
  
  Glad to hear that my blog was informative resource to your issue. Thanks for the comment!
  
  Reply
Doug F

Thanks man… Worked a treat (QNAP Nas – Win 10)

Reply
1. Aruna Lakmal
  
  Hi Doug
  
  Great! Thank you very much for the comment!
  
  Reply
Hendy Lee

Very useful! Thank you!

Reply
1. Aruna Lakmal
  
  Thank you Hendy!
  
  Reply
Prakash

Very nice , it’s working perfectly.
Thanks very much

Reply
1. Aruna Lakmal
  
  Glad to hear that I was able to help! Thanks for the comment!
  
  Reply
zoelee Chabib

Thanks, work for me….

Reply
1. Aruna Lakmal
  
  Glad to hear that 😊
  
  Reply
Daryl Schuck

Thank you, helped solve my problem of not being able to access my WD MyCloud!

Reply
1. Aruna Lakmal
  
  Great! Glad to hear that was resolved your issue.
  
  Reply
Tom Ford

Cool! I’m using a Netgear C3000-100NAS modem (Comcast) and a LaCie housing, with a WD drive,using Win 10 Pro 64 ver. 1903, and couldn’t map the drive. A comment on the Netgear Community said I had to enable SMB 1.0, but that didn’t help – your tip got it to work – with just SMB Direct, not SMB 1.0 (which isn’t secure).

Reply
1. Aruna Lakmal
  
  Nice! Glad I could help you! 😊
  
  Reply
miko

thanks so much , this very helpfull 🙂

Reply
1. Aruna Lakmal
  
  Glad to hear that it was resolved with my help!
  
  Reply
Tom Ford

Good information, and it gave me access – Thanks.. I have to admit when I first saw the term “Lanman,” I thought it only referred to the decades-old Novell product! Now that I have my USB 3.0 outboard drive working, the next step is upgrading my modem – mine has vague specs that hint at USB 2,0 High Speed, but really only has 2.0 standard; 12 mbps! That seems so slow now, but I remember upgrading hardware from the pre-standard 4 mbps to 10 mbps in 1984.

Reply
Madison Knight

Thanks so much for posting this. This was a big help to me.

Reply
1. Aruna Lakmal
  
  Hi Madision
  
  Thank you for your feedback! Glad to hear that.
  
  Reply
Kostas

Done! Worked!! Thank you very much, you saved big-big time for me!!!

Reply
1. Aruna Lakmal
  
  Hi Kostas
  
  Great! Thank you for the comment!
  
  Reply
hasniali

Thanks. It worked.

Reply
PETROS DINALIS

thank you so so much for a very helpfull solution.

Reply
1. Aruna Lakmal
  
  Thank you for the words Petros!
  
  Reply
Fred

You are an absolute legend!! Finally an end to 3 hours of frustration going from Windows 7 to Windows 10. Thankyou

Reply
1. Aruna Lakmal
  
  Thanks Fred! Appreciate the words!
  
  Reply
Ed Angel

Excellent – Thank you!!

Reply
1. Aruna Lakmal
  
  Thank you!
  
  Reply
Thu Ya Aung

Thanks for your solution and it really work in my window10 laptop.

Reply
1. Aruna Lakmal
  
  Glad to hear that! Thanks for the comment!
  
  Reply
i_Mike

Thank you! Stupid windows 10 suddenly blocked me from accessing my network drive, your solution helped!

Reply
1. Aruna Lakmal
  
  Hi Mike, ha ha yes! I was in the same shoes and glad to hear that you were able to fix it with my help!
  
  Reply
Jordan Hedberg

Thanks you!!

Reply
1. Aruna Lakmal
  
  Glad I could help!
  
  Reply
kenya

perfect … Thanks

Reply
1. Aruna Lakmal
  
  Glad to see that my post was helped you to fix the issue.
  
  Reply
Omar Faruk

Thanks! helpful.

Reply
1. Aruna Lakmal
  
  Thanks for the comment!
  
  Reply
GARY

Bingo! thanks!

Reply
1. Aruna Lakmal
  
  Thanks for the comment!
  
  Reply
Chris Jacobs

Thank you!!! Totally helpful!! Awesome post!!!!

Reply
1. Aruna Lakmal
  
  Thanks for the comment!
  
  Reply
TOM

Worked great Thank you!

Reply
Andrew

This no longer works in windows 10 2004

Reply
Andrew

I worked out why this no longer works in Windows 10 2004. The group policy editor does not change the correct value in the registry. Editing it manually worked

Navigate to: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

Set: AllowInsecureGuestAuth to 1

Reply
1. Aruna Lakmal
  
  Glad to know that, Thanks for sharing!
  
  Reply
Akinsanmi Temidayo

This is very Help. thanks.

Reply
Jib Buttkiss

I spent hours trying to get around this, your solution was the only one that worked. Thank you!!!!! 😀

Reply
kucelkj

Great article. Thank you.

Reply
Elliot

Didn’t work for me. But after much digging I found what is below on another site and it worked.

I came right using regedit. Locate: HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters and make sure “AllowInsecureGuestAuth” value is set to 1

Reply
lasantha

it’s worked. thank you

Reply
1. Aruna Lakmal
  
  Glad to hear that Lasantha, Thanks for the comment!
  
  Reply
xen

i used this gem again after a reinstall. the most useful article on the internet. Thankyou Aruna for taking the time to post it you’re a credit to the human race.

Reply
1. Aruna Lakmal
  
  Thank you for your humble words
  
  Reply
Frank

This is awesome, worked right away, thank you very very much!!!

Reply
Luckwin

Thank you, Its working.

Reply
mohammad

its very good and usefull
thanks very much

Reply
1. Aruna Lakmal
  
  Thank you!
  
  Reply
Jerry

Thanks for the resolution.. this worked for me..

Reply
1. Aruna Lakmal
  
  Thank you for the reply!
  
  Reply
Walid

Thank you !!

Reply