Windows cannot access hostname 0x80070035 the network path was not found

Windows 10 and Linux Samba Problem: “Windows cannot access \\hostname”

Last updated on

I was having an issue connecting to a shared, public folder on my Ubuntu 20.04 server. I could access it fine on two other Windows 10 PCs but not on another.

Samba Shares Inaccessible

When trying to open a network Samba share, I kept getting this error:

Network Error: Windows cannot access \\hostname. Check the spelling of the name. Otherwise there might be a problem with your network. To try and identity and resolve network problems, click Diagnose.

0x80070035 the network path was not found

Running net use in Windows Command Prompt brought up another error.

c:\net use \hostname

System error 1272 has occurred.
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.

This error is due to Windows Local Group Policy restrictions not allowing access to “insecure guest logins”. It seems Microsoft decided to disable access by default in new Windows Updates.

According to a post from Microsoft, they say:

Guest access in SMB2 disabled by default in Windows
A malicious computer that impersonates a legitimate file server could allow users to connect as guests without their knowledge. Microsoft recommends that you do not change this default setting. If a remote device is configured to use guest credentials, an administrator should disable guest access to that remote device and configure correct authentication and authorization.

If you are aware of the security implications and have to have guest access to your Samba shares, you can re-enable it in Group Policy.

Edit Group Policy

Open the Windows 10 Start Menu and type gpedit.msc, then press Enter.

Enable insecure guest logons

In the left-hand tree, expand Computer Configuration > Administrative Templates > Network > Lanman Workstation.

Double-click Enable insecure guest logons.

Windows 10 Enable insecure guest logins policy

Toggle the radio button to Enabled and then click OK.

Enable “Digitally sign communications (always)”

In the left-hand tree, expand Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

Double-click Microsoft network client: Digitally sign communications (always) and set it to Disabled. Click OK.

That’s it. You should now be able to access your network share.

1 Star2 Stars3 Stars4 Stars5 Stars 3.40 (10 votes)

Let me know if this helped. Follow me on Twitter, Facebook and YouTube, or 🍊 buy me a smoothie.

p.s. I increased my AdSense revenue by 200% using AI 🤖. Read my Ezoic review to find out how.

22 replies

avatar
  Subscribe  
newest oldest
Notify of
Bear
Guest
Bear
Bear
4 days ago

Nope not working

Dan
Guest
Dan
Dan
2 months ago

wow that worked, thank you so much!

homer
Guest
homer
homer
3 months ago

thanks this was a big big help if you have legacy old linux hardware on your network; i became a computer god to these people now:)

Eloi
Guest
Eloi
Eloi
3 months ago

Worked.
Thank you

MR0002
Guest
MR0002
MR0002
5 months ago

For me, the solution was to update the registry and set both AllowInsecureGuestAuth to 1 and RequireSecuritySignature to 0, all the threads that came up in my searches (and I tried for hours) mentioned setting AllowInsecureGuestAuth to 1 or changing the Enable insecure guest logons in the group policy as this article details, but none of this worked for me until I also set RequireSecuritySignature to 0. I’m running the latest May 2020 Win10 Update build (version 2004), as soon as I set this additional registry setting I was able to connect to my share without issue, no restart needed. I was connecting to a WD MyCloud Home public drive from my work laptop while at home, and the MyCloud Home doesn’t allow you to set creds for the SMB Public drive – below are the registry settings that FINALLY resolved the issue.

One other note, there were additional firewall and network sharing / discovery controls on my machine, within Network and Sharing I had to change my home WiFi network to be marked as a Private Network instead of a Public Network – the additional restrictions were specific to Public networks, changing to Private resolved it.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParameters]

“AllowInsecureGuestAuth”=dword:00000001
“RequireSecuritySignature”=dword:00000000

deyo
Guest
deyo
deyo
4 months ago

saved my time and nerves …..thanks a lot for this solution .

gas
Guest
gas
gas
3 months ago

Thank you!

Tried everything, but I guess this was the final step to get it working….

Iam
Guest
Iam
Iam
2 months ago

Excellent!

Henri
Guest
Henri
Henri
2 months ago

Excellent work!

ptwat
Guest
ptwat
ptwat
2 months ago

This is the solution that worked for me! Thanks for posting. I had Windows10 Home versions that were not getting error, but main PC is Windows10 Pro and threw an error every time. Changing “AllowInsecureGuestAuth” to “1” fixed it. Interestingly Home does not have this Registry value avoiding the problem.

Anvan
Guest
Anvan
Anvan
1 month ago

Getting done by editing the registry by your discussion. Thanks a lot.

Genesis
Guest
Genesis
Genesis
6 months ago

you are awesome!!!!

Miso
Guest
Miso
Miso
6 months ago

not working

Tolga Erok
Guest
Tolga Erok
Tolga Erok
7 months ago

Thank christ a super easy solution!

argayuavy
Guest
argayuavy
argayuavy
8 months ago

you’re magic…. success

Damin Mark Sexton
Guest
Damin Mark Sexton
Damin Mark Sexton
9 months ago

OMG!

I have tried so many things off the internet! This one worked straight off the bat!

You are a magician!

Thank you so much!

Joao
Guest
Joao
Joao
9 months ago

Did the trick beautifully, thanks!

maceffi
Guest
maceffi
maceffi
9 months ago

did not work for me

josep
Guest
josep
josep
2 months ago

for me neither.

KipM
Guest
KipM
KipM
1 month ago

Same