Fix Error Code: 0x80070035 The network path was not found

Fix Error Code: 0x80070035 The network path was not found

If you have a NAS storage drive which can't be detected on your windows computer I will show you a way on how to fix the error 0x80070035. it's a very common error and can be a nightmare to fix if you don't know how.

If you are running Microsoft Windows operating systems, it will allow your computer to share data and access data files on each other’s computer. But you could run into problems and see the message saying that Error code: 0x80070035. The network path was not found.

This error could be caused by many things, so I made a video to help you troubleshoot and get your problem solved!

1. Go to Local Policies - Security Options -Network security: and look for LAN Manager Network security: LAN Manager authentication level. Now change this to Send LM & NTLM-use NTLMv2 session security if negotiated.
2. Enable NetBIOS over TCP/IP:
. Go to “Control Panel\Network and Internet\Network Connections”.
. Right-Click on the connection and choose Properties.
. Click “Internet Protocol (TCP/IP) Version 4”.
. Click Properties, and then click Advanced.
. On the Advanced TCP/IP settings windows, go to “WINS” tab.
. Under NetBIOS setting, click “Enable NetBIOS over TCP/IP”, on all computers and then click OK.

3. Enable TCP/IP NetBIOS Helper in Services, also make sure it's running.

4. Open regedit and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Now delete HardwareID and Store keys.
(You can export these before you delete them if you wish)

Need more help? why not join my forum

[CountSabazios]

Nothing of the above-mentioned worked for me, but luckily I found a solution. I'll put it here just in case:

In "Local Group Policy Editor" - Computer Configuration > Administrative Templates > Network > Lanman Workstation - Enable insecure guest logons: Not configured (by default) switch to *Enabled*

Weird that it was the "Error 0x80070035 The network path was not found" pop-up and not the one saying that unauthenticated guest access is blocked by security policies.

[deonholt]

Thanks for this video. Unfortunately I'm still stuck with error 0x80070035. I have already worked through your other video on "The network path was not found". Anything else I can try except for fresh installation of Win 10 Pro 64-bit?

[pzn]

Hi there, by far you have the best video for solve this issue. There's one thing you can add to your video that can help many people once it was the only thing that solved the issue in my Win10/Seagate Personal Cloud and it's related do saved credentials. Follow this: Control Panel > User Accounts and Family Safety > Credential Manager - then select Windows Credentials and look for saved credentials (should be the same as the login name used for the Seagate Personal Cloud/ NAS web interface). Afterwards go to map network driver and try again (in my case I had to click on "Connecting using a different user name". Good luck for all.

[inflightstudio]

You deserve a comment of gratitude. I have tried many suggestions, to an extent that I started to lose an overview of what combinations I have already tried. Following your steps resolved my issue connecting my Synology DS918+ NAS system in Windows 10 1709. Before this fix, I could only see it and access through a browser but not through Windows Explorer. Thank you very much.

[profuse]

deleting those folders in regedit worked for me.

background: fresh install of win 10 64bit; spent a week trying to map the NAS network drive; this video helped.

[SuperJamesus]

thank you so much for video. just to add i followed all the steps and nothing was working, i then turned my wi-fi adaptor off and boom, NAS drive came to life. turned wi-fi back on and its all working fine. saved your videos for any future trouble shooting. very clear and helpful. many thanks.

[deebee]

I had this problem on a new install of Win 7 Pro, tried to find answers to fix this online with no success. I then I remembered how you solved another hard problem for me years ago. You will always be my first search from now on.Thank you this worked

[Maldeus]

"0x80070035 network path not found"
Solution:
gpedit.msc > Computer Config > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons > Enable

[samuelhaines]

I came across this SOLUTION after half a day of doing everything else (the same 5 steps this video and many others show). I'm grateful to the video creator here. It's all helpful and good. Just not what I needed.


FOR EVERYONE WHO IS STILL STUMPLED....Try this...(This applies to DSM Synology)



OP: Can you share the step to mount missed folder? I had similar issues, not all folder missing after DSM updates.
Solution: Just figured this out myself after a brief panic after not seeing my encrypted folders:



In DSM:
Go to Control Panel
Select Shared Folder from the sidebar
Choose your encrypted folder
Select the 'Encyption' dropdown menu and choose "Mount"

[celticlofts]

One little utility you could use is wireless network watcher. It will tell you the IP addresses of everything connecting to your network, in real time. If the drive your trying to connect to isn't listed then power off your media server or whatever you're having problems trying to connect to - Power it back on and check to make sure the IP address shows up in the Wireless Network Watcher utility. Once it does then you know you don't have a hardware of cabling issue and you can proceed to follow the instructions listed in the video. Good video by the way.

[janinegrosenick]

OMG, I can't believe this has an end now, been looking for a solution for days! Deleting those files solved the issue! THANKS SO MUCH!

[pwoodwardc]

Brilliant! Tried following several other YouTube videos with no success before following your suggestions. I was only successful when I implemented your very last, almost afterthought suggestion, and nearly didn't bother watching all the way through to the end. As some ppl have said following your suggestions hasn't worked for them, it might be better to simply itemise all your procedures, in case they give up before this final suggestion. Anyway, many thanks for doing this guide, it's the only one I have found that achieves access to my NAS in Windows 10.

[mohawahba]

I have done everything and it's still the same issue. I can't access other computers but they can access mine except for one computer

[orvillepike]

Finally a video that shows a "real" solution for a network not working. A 10 minutes solution after looking hours for videos that all say the same thing and don't fix anything.

Thanks a million.

[leonel-pedro]

Hi, thank you for the great video, I follow all the steps but no luck, any other suggestions please?
Thanks!

[FiryPhnx]

Super clear, step-by-step and thorough instructions. Worked perfectly! Thank

[kdpba]

These are all great ideas and a demonstration of good troubleshooting. Not splitting hairs here but, I have been doing this a long time. Could be something else as well! While I am a Linux guy I do actually use Windows and OSX as well. I too had run into this issue and it frustrated the hell out of me. If None of this worked for you, here is what you will need to do. NOTE, SMBv1 is VERY INSECURE, for this reason it has been disabled. Your NAS provider, mine is Seagate, should provide a firmware update to fix this issue by updating the NAS to use Version 2. My NAS was discontinued and runs OpenWRT so, I could update it manually being its mostly open source but its a pain in the ass. That said you too will likely not be able to update your NAS. If its an actual file server then yes you need to update it instead of doing this. 1) We need to open Control Panel, so you can either type Control Panel in the search box or right click the start button choose run and type Control Panel. 2)Click on "Programs" then Click "Turn Windows Features on or off" ( Under the heading "Programs"). Scroll down just below SNMP to SMB 1.0/CIFS File Sharing Support. You can check the Box for this option, it has likely been unchecked as a security measure. Checking this box enables the client and server using protocol 1. Ideally you really only need the client enabled. Once done reboot. You should be able to access NAS and or server folder again. Cisco Content Security Engineer, CPT, CEHv8.

[Cltronix]

Nothing worked for me. Then I found this for my Synology NAS: Login to your NAS website: Control Panel > File Services > Advanced Settings > Maximum SMB Protocol: Set this to SMB3 > Apply
THIS did work for me!

[MarianZburlea]

It worked! thanks a lot:
Go to Local Policies - Security Options -Network security: and look for LAN Manager Network security: LAN Manager authentication level. Now change this to Send LM & NTLM-use NTLMv2 session security if negotiated.

[balmesz]

Worth to try to enable SMB V1 for Win10: Control Programs > Programs and Features > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support