After upgrading the Windows 10 construct to 1803 or larger (1809, 1903, 1909), some customers seen that they may now not hook up with shared community folders on neighboring computer systems or on NAS units.
Windows File Explorer can not even show a listing of shared folders on community computer systems (each operating Windows 10 and Windows 7). When attempting to open any community folder, an error seems:
Windows can not entry sharedNAS
Check the spelling of the title. Otherwise, there is perhaps an issue together with your community. To attempt establish and resolve community issues, click on Diagnose.
Error code: 0x80070035.
The community path was not discovered.
At the identical time, you may simply open and join community shared folders from different computer systems (operating older variations of Windows 10, eight.1, or 7), smartphones and different units.
Let’s attempt to determine the best way to repair the error with the code “
0x80070035. Network path not discovered” in Windows 10.
SMBv1 is not Installed by Default in Windows 10
First of all, it is advisable to perceive whether or not the issue is expounded to the truth that in Windows 10 1709 and newer the unsafe legacy SMB v1.zero protocol is disabled by default (this protocol is used to entry community shared information and folders in native community). If you attempt to hook up with a community machine that solely helps entry over SMBv1 protocol (for instance, an previous model of NAS storage, a pc operating Windows XP/Windows Server 2003) from the latest Windows 10 builds, you received’t have the ability to hook up with shared community folders on such a tool. And when accessing the useful resource by the UNC path (
NASname), you may obtain the error “0x80070035”.
To test if the SMBv1 protocol is enabled in Windows 10, use the next command:
Dism /on-line /Get-Features /format:desk | discover "SMB1Protocol"
As you may see, on this case the SMB1Protocol-Client characteristic is disabled.
SMB1Protocol | Disabled SMB1Protocol-Client | Disabled SMB1Protocol-Server | Disabled
You can allow the legacy SMB consumer to entry community units utilizing SMBv1 protocol by way of the Control Panel (Control Panel -> Programs and Features -> Turn Windows options on or off -> SMB 1.zero / CIFS File Sharing Support-> SMB 1.zero / CIFS Client). In addition, you may entry the options set up dialog by operating the
Or you may allow the SMB 1 consumer with the DISM command:
Dism /on-line /Enable-Feature /FeatureIdentify:"SMB1Protocol-Client"
After putting in the SMBv1 consumer, it is advisable to restart the pc and test if entry to the community folder has appeared.
On Windows 10 1709 and newer the SMBv1 consumer is mechanically eliminated if it has not been used for greater than 15 days.
Enable Insecure Guest Logons
If you utilize to attach NAS or different computer systems, it is advisable to allow the . In Windows 1803/1709 it blocks entry to shared community folders over the SMB 2.zero protocol underneath an nameless (visitor) account. To do that, within the , allow the Enable insecure visitor logons coverage within the GPO part: Computer Configuration -> Administrative templates -> Network -> Lanman Workstation.
Or you may allow SMB community entry underneath visitor account by way of the registry utilizing the command:
reg add HKLMSYSTEMCurrentControlSetProvidersLanmanWorkstationParameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /f
Disable SMB1 and SMB2 Protocols in Windows
If solely SMB v3 units are used in your community (Windows eight.1 / Windows Server 2012 R2 and newer, see ), you may repair the 0x80070035 error by disabling legacy SMB1 and SMB2 protocols. The reality is that your laptop could attempt to use the SMB 2.zero protocol to entry community folders that permit solely SMB three.zero connections (probably with ).
First via the Control Panel or utilizing the instructions within the PowerShell console:
sc.exe config lanmanworkstation rely= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 begin= disabled
Dism /on-line /Disable-Feature /FeatureIdentify:"SMB1Protocol"
Then disable the SMB 2.zero protocol:
reg.exe add "HKLMSYSTEMCurrentControlSetprovidersLanmanServerParameters" /v "SMB2" /t REG_DWORD /d "zero" /f
sc.exe config lanmanworkstation rely= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 begin= disabled
Set-SmbServerConfiguration –EnableSMB2Protocol $true
You can confirm that the SMB 1 and SMB 2 protocols are disabled by operating the next PowerShell command:
Get-SmbServerConfiguration | choose "*enablesmb*"|fl
EnableSMB1Protocol : False EnableSMB2Protocol : False
Check the Network Discovery Configuration on Windows 10
If your computer systems are joined to a workgroup, I strongly advise you to comply with the suggestions from the article .
In the Network and Sharing Center part of the Control Panel on each computer systems, confirm that the Private profile is used as the present profile (Private (Current profile)). Make positive that the next choices are enabled:
- Turn on community discovery + Turn on computerized setup of community related units;
- Turn on file and printer sharing.
In the All Networks part, allow the next choices:
- Turn off password Protect Sharing;
- Turn on sharing.
On each computer systems, reset the DNS cache:
And reboot each computer systems.
What else is value testing:
- In the properties of the (each on the NTFS file system permissions and the shared folder degree), confirm that the Everyone group has the permissions to learn the contents of the folder;
- Check if the community storage (laptop with a shared folder) is accessible by an IP handle. To do that, within the File Explorer, enter
192.168.1.100and press Enter (change with the IP handle of your community storage or distant laptop);
- If you concurrently have two energetic community interfaces in your machine (Wi-Fi and Ethernet), attempt to briefly disable certainly one of them and test entry to your native community sources;
- Verify that the next providers are operating in your laptop (open the
providers.mscconsole). Try to begin these providers and alter startup sort to the Automatic Delayed Start:
- Function Discovery Provider Host – fdPHost
- Function Discovery Resource Publication – FDResPub
- SSDP Discovery – SSDPSRV
- UPnP Device Host – upnphost
- DNS Client (dnscache)
- Try to briefly disable your antivirus and/or firewall utility and test if the issue persists whereas accessing the community sources;
- Try to vary the pc title within the System properties;
- Try to disable the IPv6 protocol within the properties of your community adapter within the Control Panel;
- Try to reset the TCP/IP community stack on the pc with instructions:
netsh winsock reset
netsh int ip reset
- Run the PowerShell console and test the provision of the SMB port on the distant laptop utilizing the cmdlet ( community entry could also be blocked by a firewall):
Test-NetConnection 10.16.1.70 -port 445(if the firewall is not limit SMB site visitors, the standing ought to seem TcpTestSucceeded : True).
Access NAS and Samba Storage from Windows 10 with Saved Credentials
If the issue happens solely once you accessing the NAS (or Samba server on Linux), you may attempt to save the NAS connecting password to the Windows Credential Manager (Control PanelAll Control Panel GadgetsCredential ManagerAdd a generic credential).
Then in Network and Sharing Center within the Advanced sharing settings allow the choice Use person accounts and passwords to hook up with different computer systems.
I hope my article can be helpful, and you’ll restore entry to your shared folders in your LAN.