Network Attached Storage (NAS) basically helps you to share the data across machines in a localized environment. NAS uses file sharing specific protocols for this purpose. So using this phenomenon, you can simply connect your Windows 10 using HomeGroup or WORKGROUP. This will help you to share the content instantaneously across the machine with less efforts required.
However, some clients or users may experience network related issues while accessing the NAS/share(s). Today, in this article, we’ll address such an issue. Here is the message, we recently came around while accessing the share:
Page Contents
Windows cannot access <the share>
Error code: 0x80070035
The network path was not found.
This this error is expected to occur if NetBIOS over TCP/IP is not enabled on the machine. However, other factors may also involve and cause this issue. So users victim of this problem may try below mentioned suggestions and see if they could help to suppress the issue.
FIX: The Network Path Was Not Found (0x80070035) In Windows 10/8.1/8/7
FIX 1 – General Suggestions
1. Make sure your system using Server Message Block (SMB) protocol version 1. SMBv1 protocol can be enabled using either ways mentioned in this post.
2. Ensure that following services are Running and set to Automatic Startup type:
- DCHP Client
- Homegroup Listener
- Homegroup Provider
- Net.Tcp Port Sharing Service
- Network Connections
- Network List Service
- Network Location Awareness
- TCP/IP NetBIOS Helper
3. Temporarily disable the third-party security software such as antivirus etc. and check the issue status.
4. In Device Manager, expand your network adapter, right click and select Uninstall. Then click Action > Scan for hardware changes. This should reinstall the adapter and see if the problem appears then.
5. Go to Control Panel > All Control Panel Items > Credential Manager > Add a Windows Credential and type name of each machine, its user and corresponding password. After saving credentials the problem may be solved.
6. Navigate to Control Panel > All Control Panel Items > Network and Sharing Center > Advanced sharing settings. Under Private profile, for HomeGroup Connections, select Use user accounts and passwords to connect to other computers option. Click Save changes and exit Control Panel.
If you still have the issue, try FIX 2.
FIX 2 – Enable NetBIOS over TCP/IP
1. Press 
+ R to open Run, type ncpa.cpl and click OK.
2. In Network Connections window, right click on your primary network adapter and select Properties.
3. Next, on the property sheet, at Network tab, select Internet Protocol Version 4 (TCP/IPv4) and hit Properties.
4. On TCP/IPv4 property sheet, click Advanced button.
5. Finally, on Advanced TCP/IP Settings sheet, on WINS tab, under NetBIOS setting, check Enable NetBIOS over TCP/IP option. Click OK and return to Desktop.
This should fix the issue significantly and you may now be able to access the share without any error.
Hope something helps!
Related fix: The network location can’t be reached (error 0x800704cf).
12 Comments
Add your comment
It just happened yesterday after the Windows 10 update. Somehow Windows disable the NetBIOS setting so I couldn’t access any network resources but internet. User the default setting resolves the issue. Thank you so much so pointing to the right direction!
^^ Glad the issue is resolved 😊
Hi one of my job which will run and place the file in my NAS share. But due to some reason the job got failed with error message network path could not found.
We suspect that this is because NAS unavailable during that time.
Kindly help us what could be the cause and how we need to troubleshoot this
^^ You can try above mentioned suggestions and see if they helps!
Can i try this fix to my server machine? please reply.
^^ Yup!
My problem was solved after the checklist of the very second step (2): a service was not running.
Thank you very much
^^ Glad to help Armando!
I am working on a similar issue. We are on a domain, and a few random users cannot save in to their my document locations on the server. To which I mean they cannot be in an application and hit save or save as and point to their network location. They can however save new documents in to the root of their share, but they cannot save as an existing document even diving it a different name. Error form Word 2016: \\~~ServerPath~~\USER\NAME\Documents\TEXT.DOCX Path does not exist. Check the path and try again. The path does indeed exist. We can navigate to the location in File Explorer. We can save to the desktop and copy them to the network share and we do not get any error. I have gone through so many “fixes” form M$ nothing seems to help. One machine out of the 3 worked by turning off the windows feature for smb v1 and then turning it back on rebooting each time.
^^ Thanks Tad for adding this!
Holy Cheetos! “Add a Windows Credential” actually fixed it for me!! Thanks~!`
^^ Glad it worked!