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

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

Last updated on | 34 replies

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

Public Samba Shares Inaccessible

When trying to open a network public 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 due to security issues.

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 want to allow guests to access your public Samba shares, you can re-enable it in regedit.

Regedit: Set AllowInsecureGuestAuth to 1

Click the Start Menu, type regedit and open it in administrative mode.

In regedit, press Control + F and search for AllowInsecureGuestAuth. This may take a minute or so to return a result.

Windows 10 and Linux Samba Problem: "Windows cannot access \\hostname"

When you get a result, change AllowInsecureGuestAuth to 1.

Windows 10 and Linux Samba Problem: "Windows cannot access \\hostname"

Press Control + F again and click Find Next.

Windows 10 and Linux Samba Problem: "Windows cannot access \\hostname"

When you get a result, change AllowInsecureGuestAuth to 1.

Press Control + F again and click Find Next, and repeat the above steps until you have changed all instances in regedit of AllowInsecureGuestAuth to 1. In most cases, there are only two entries in regedit.

Regedit: Set RequireSecuritySignature to 1

In regedit, press Control + F and enter RequireSecuritySignature.

Under the Look at checkbox group, uncheck all boxes except for Value and click Find Next.

This may take a minute or so to return a result.

Windows 10 and Linux Samba Problem: "Windows cannot access \\hostname"

When you get a result, change RequireSecuritySignature to 1.

Windows 10 and Linux Samba Problem: "Windows cannot access \\hostname"

Press Control + F again, click Find Next and repeat the above steps until you have changed all instances in of RequireSecuritySignature to 1. In most cases, there are only two entries in regedit.

That’s it, you’re done. You should now be able to access your network share. You may need to restart the Windows 10 machine for changes to take effect.

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.

34 replies

Leave a reply

Your email address will not be published. Required fields are marked *

  1. I spent a late evening pulling my hair out trying to resolve this issue. I tried everything posted in this thread and many other suggestions without success. I was almost ready to wave the white flag when I figured it out myself. Hopefully this will help some of you who have been unsuccessful so far:

    1. Go to the Windows Control Panel and under Programs select “Turn Windows Features On or Off”. Scroll down to “SMB 1.0/CIFS File Sharing Support” and place a checkmark beside this and click “OK”. It will then Search for the required files and apply the changes. Select “Restart Now” when prompted.

    2. Click the START menu and type “regedit” and select “Run as Administrator”.

    Go to the following location:

    ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftPolicyManagerdefaultLanmanWorkstationEnableInsecureGuestLogons

    Double click on “value” and change the value data from 0 to 1 and select “OK”.

    You may want to reboot at this point but I was able to access the SAMBA share immediately after changing this value. It is part 2 of my instructions above that seemed to be the special sauce. I had found many suggestions to turn on the SMB 1.0 feature, as well as suggestions to make changes to the Local Group Policy or using regedit to modify parts of the registry, but not the specific registry address referenced above. This is what worked for me and I hope that it makes life easier for someone else.

    As an added note, my computers were running Winsows 10 Pro version 2004 and 20H2.

    1. Thanks for the comment. However, my article was written to prevent people from re-enabling the unsecure SMB 1 protocol. I would never advise that users enable SMB 1 in Windows 10 as it opens up the OS to security holes. Microsoft disabled it through Windows Update for a very good reason.

      I would point people to this article if you are having issues viewing Samba shares from Windows 10. https://devanswers.co/discover-ubuntu-machines-samba-shares-windows-10-network/

  2. This guide has been updated as per recomedations by commenter MR0002 below.

    It appears that gpedit.msc does not update all settings in regedit as required. Also, Windows 10 Home edition does not have gpedit.msc at all, so all updates must be done through regedit.

    Hope this helps.

  3. 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:)

  4. 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

    1. 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.

    2. Thank you! this helped me in getting the answer for my system. I did a search of RequireSecuritySignature and chamged all the instances to 0. I had to reconnect the network share because the browse gadget did not found it, then it was routine, login, password and connected! Thanks!

    1. Why does Windows more and more require regedit? It takes me ages to find keys and values described in such tweaks and 95% of the time, I neeed to create a non-sense DWORD. This is time consuming and error prone. Why aren’t there GUI tools to configure these options? I just cannot go on. This is over complicated and I’m about to bang my head over a wall. I just want to transfer data from my old computer to a new, made the stupid mistake of choosing a case that can just accept two drives and thus cannot add my old PC’s drive temporarily even though that looks to be the only solution. External hard drives are super super super slow, taking more than twenty minutes simply to copy a few gigabytes of data. I’m just done, I cannot continue like this (and yes this is supposed to be a USB3 external drive the ones I tried).

  5. 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!

        1. It fixed access from this Win10 computer to others, but not my other computers to this Win10 computer. Half fixed.