Error code 0x80070035: the network path was not found

-

After upgrading the Windows 10 build lớn 1803 or higher (1809, 1903, 1909), some users noticed that they could no longer connect to lớn shared network folders on neighboring computers or NAS devices.

Bạn đang xem: Error code 0x80070035: the network path was not found


Windows File Explorer cannot even display a các mục of shared folders on network computers (both running Windows 10 & Windows 7). When trying to lớn open any network thư mục, an error appears:


Network ErrorWindows cannot access \sharedNASCheông chồng the spelling of the name. Otherwise, there might be a problem with your network. To try identify & resolve sầu network problems, clichồng Diagnose.Error code: 0x80070035.The network path was not found.

*

At the same time, you can easily open và connect network shared folders from other computers (running older versions of Windows 10, 8.1, or 7), smartphones và other devices.

Let’s try khổng lồ figure out how lớn fix the error with the code “0x80070035. Network path not found” in Windows 10.


SMBv1 is not Installed by Default in Windows 10

First of all, you need to underst& whether the problem is related to the fact that in Windows 10 1709 và newer the unsafe legacy SMB v1.0 protocol is disabled by default (this protocol is used khổng lồ access network shared files và folders in local network). If you try to connect to lớn a network device that only supports access over SMBv1 protocol (for example, an old version of NAS storage, a computer running Windows XP/Windows Server 2003) from the lathử nghiệm Windows 10 builds, you won’t be able lớn connect khổng lồ shared network folders on such a device. And when accessing the resource by the UNC path (\NASname), you can receive the error “0x80070035”.

To check if the SMBv1 protocol is enabled in Windows 10, use the following command:

Dism /online /Get-Features /format:table | find "SMB1Protocol"

*

As you can see, in this case the SMB1Protocol-Client feature is disabled.

SMB1Protocol | DisabledSMB1Protocol-Client | DisabledSMB1Protocol-Server | DisabledYou can enable the legacy SMB client khổng lồ access network devices using SMBv1 protocol via the Control Panel (Control Panel -> Programs and Features -> Turn Windows features on or off -> SMB 1.0 / CIFS File Sharing Support -> SMB 1.0 / CIFS Client). In addition, you can access the features installation dialog by running the optionalfeatures.exe cộ command.

*

Or you can enable the SMB 1 client with the DISM command:

Dism /online /Enable-Feature /FeatureName:"SMB1Protocol-Client"

*

After installing the SMBv1 client, you need to lớn restart the computer và kiểm tra if access to lớn the network folder has appeared.


Important! When you enable the SMB1 client, và especially SMB1-Server, keep in mind that this protocol is vulnerable and has a large number of remote exploitation vulnerabilities. If you don’t need the SMB v1 protocol lớn access legacy devices, be sure khổng lồ disable it.

On Windows 10 1709 và newer the SMBv1 client is automatically removed if it has not been used for more than 15 days.

Enable Insecure Guest Logons

If you use anonymous access to lớn connect NAS or other computers, you need lớn enable the insecure guest logon policy. In Windows 1803/1709 it blocks access khổng lồ shared network folders over the SMB 2.0 protocol under an anonymous (guest) account. To bởi this, in the Windows 10 Local Policy Editor (gpedit.msc), enable the Enable insecure guest logons policy in the GPO section: Computer Configuration -> Administrative sầu templates -> Network -> Lanman Workstation.

Xem thêm: Chia Sẻ Xin Code Zing Mp3 Vip 2021 Miễn Phí Và Mới Nhất Cho Người Sử Dụng

*

Or you can enable SMB network access under guest trương mục via the registry using the command:

reg add HKLMSYSTEMCurrentControlSetServicesLanmanWorkstationParameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /f

Disable SMB1 và SMB2 Protocols in Windows

If only SMB v3 devices are used on your network (Windows 8.1 / Windows Server 2012 R2 and newer, see the table of SMB versions in Windows), you can fix the 0x80070035 error by disabling legacy SMB1 & SMB2 protocols. The fact is that your computer may try to lớn use the SMB 2.0 protocol khổng lồ access network folders that allow only SMB 3.0 connections (possibly with traffic encryption).

First disable the SMB v1.0 protocol through the Control Panel or using the commands in the PowerShell console:

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsisc.exe config mrxsmb10 start= disabledDism /online /Disable-Feature /FeatureName:"SMB1Protocol"

Then disable the SMB 2.0 protocol:

reg.exe cộ add "HKLMSYSTEMCurrentControlSetservicesLanmanServerParameters" /v "SMB2" /t REG_DWORD /d "0" /fsc.exe cộ config lanmanworkstation depend= bowser/mrxsmb10/nsisc.exe cộ config mrxsmbtrăng tròn start= disabledPowerShell -ExecutionPolicy UnrestrictedSet-SmbServerConfiguration –EnableSMB2Protocol $true

You can verify that the SMB 1 and SMB 2 protocols are disabled by running the following PowerShell command:

Get-SmbServerConfiguration | select "*enablesmb*"|fl

EnableSMB1Protocol : FalseEnableSMB2Protocol : False

*

Cheông chồng the Network Discovery Configuration on Windows 10

If your computers are joined to lớn a workgroup, I strongly advise you to lớn follow the recommendations from the article Network computers not showing in Windows 10.

In the Network and Sharing Center section of the Control Panel on both computers, verify that the Private network profile is used as the current protệp tin (Private (Current profile)). Make sure that the following options are enabled:

Turn on network discovery + Turn on automatic setup of network connected devices;Turn on file và printer sharing.

*

In the All Networks section, enable the following options:

Turn off password Protect Sharing;Turn on sharing.

On both computers, remix the DNS cache:

ipconfig /flushdns

And reboot both computers.

What else is worth checking out:

Chechồng if the network storage (computer with a shared folder) is accessible by an IP address. To do this, enter \192.168.1.100 in the File Explorer và press Enter (replace with the IP address of your network storage or remote computer);If you simultaneously have two active network interfaces on your device (Wi-Fi và Ethernet), try khổng lồ temporarily disable one of them and check access to your local network resources;Verify that the following services are running on your computer (open the services.msc console). Try khổng lồ start these services & change startup type lớn the Automatic Delayed Start:Function Discovery Provider Host – fdPHostFunction Discovery Resource Publication – FDResPubSSDPhường Discovery – SSDPSRVUPnPhường Device Host – upnphostDNS Client (dnscache)Try khổng lồ temporarily disable your antivirut and/or firewall application & kiểm tra if the problem persists while accessing the network resources;Try lớn change the computer name in the System properties;Try to disable the IPv6 protocol in the properties of your network adapter in the Control Panel;
*
Try to remix the TCP/IPhường network staông xã on the computer with commands:netsh winsock resetnetsh int ip reset

Access NAS and Samtía Storage from Windows 10 with Saved Credentials

If the problem occurs only when you accessing the NAS (or Samba VPS on Linux), you can try to save sầu the NAS connecting password khổng lồ the Windows Credential Manager (Control PanelAll Control Panel ItemsCredential ManagerAdd a generic credential).

*

Then in Network và Sharing Center in the Advanced sharing settings enable the option Use user accounts & passwords khổng lồ connect to lớn other computers.

*

I hope my article will be useful, and you will restore access lớn your shared folders on your LAN.