NasDrives.ca

Why does my NAS say "network path was not found"?

In short · as of July 22, 2026

Error 0x80070035 usually means Windows reached the NAS but refused the connection under its security policy (blocked guest access or SMB signing mismatch), or that name resolution/SMB discovery failed. Fix it by connecting with a real NAS account by hostname, ensuring SMB2/3 and signing are enabled on the NAS, and enabling network discovery.

Last verified July 22, 2026 · 2 official sources checked Updated

"The network path was not found" (error 0x80070035) is a catch-all Windows shows for several distinct problems. Work through them from most to least common on a modern PC.

1. Security policy refused the connection

On Windows 11, the usual cause is that Windows reached the NAS but declined the connection — blocked unauthenticated guest access, or an SMB signing mismatch. Microsoft lists 0x80070035 among the errors seen when guest access is blocked. Fix: connect with a real NAS username and password, and enable SMB signing on the NAS.

2. SMB1 vs SMB2/3

If the NAS only offers the obsolete SMB1 protocol, Windows 11 (which ships without SMB1) can't connect. Enable SMB2/SMB3 on the NAS.

3. Name resolution or discovery

What not to do

Don't disable the firewall or SMB signing as a shortcut. The secure path is a valid account plus SMB2/3 with signing on the NAS. And whatever the connection problem, keep the data behind the share backed up.

Fix the connection, then protect the data

Once you can reach the NAS again, make sure the storage underneath it is sound — the right drives, healthy and backed up.

Related questions

Sources

Every technical claim on this page is checked against manufacturer and standards documentation. Dates are when each source was last reviewed.