Windows Cannot Access a Shared Folder: Error 0x80070035

Error 0x80070035: The network path was not found means Windows could not complete the path from your PC to the requested share. The fastest diagnosis is to determine which layer failed: network reachability, computer-name resolution, the share itself, firewall policy, or SMB negotiation.

1. Confirm the path is written correctly

A Windows network path should look like:

\\OFFICE-PC\SharedFolder

The first name is the host computer. The second is the published share name, which can differ from the folder's local name.

On the host PC, list published shares without changing them:

Get-SmbShare | Select-Object Name, Path, Description

Administrative shares may be hidden or unavailable to a standard account, so test the intended named share.

2. Separate name resolution from connectivity

First test whether Windows can resolve the host name:

Resolve-DnsName OFFICE-PC -ErrorAction SilentlyContinue
Test-Connection OFFICE-PC -Count 2

Then try the share using the host's current IP address:

\\192.168.1.25\SharedFolder

If the IP path works but the computer-name path fails, the share and SMB service are reachable. Focus on DNS, NetBIOS or local discovery instead of changing folder permissions.

3. Check the network profile and discovery state

File sharing is normally appropriate on a trusted Private network, not a public network such as an airport or cafe Wi-Fi connection.

Inspect the active profile:

Get-NetConnectionProfile | Select-Object InterfaceAlias, NetworkCategory, IPv4Connectivity

On a trusted home or office network, confirm Network discovery and File and printer sharing are enabled in Advanced sharing settings. On a managed work PC, organization policy may control these settings.

4. Verify the host services and firewall rules

The host must be running the components that publish and discover shares. Inspect their current state:

Get-Service LanmanServer, LanmanWorkstation, FDResPub, fdPHost |
  Select-Object Name, Status, StartType

Also check whether the Windows firewall has enabled rules for File and Printer Sharing on the active profile. Do not turn off the entire firewall as a first test; that removes useful protection and does not identify the specific blocked rule.

5. Confirm modern SMB is available

Windows 10 and 11 support current SMB versions. Check the client and server configuration before changing protocol settings:

Get-SmbClientConfiguration | Select-Object EnableSecuritySignature, RequireSecuritySignature
Get-SmbServerConfiguration | Select-Object EnableSMB2Protocol, EnableSecuritySignature

Do not enable SMB 1.0 as a routine fix. SMB 1.0 is obsolete and less secure. If an old storage device requires it, updating or isolating that device is safer than weakening every Windows connection.

6. Interpret the timing of the error

• An immediate 0x80070035 response often points to a bad path, unavailable share, or local policy.
• A long wait can point to name resolution, routing, VPN, sleeping hardware, or firewall timeouts.
• A credential prompt means Windows reached an authentication stage; follow the separate network-credentials diagnosis instead.

How Againly approaches this problem

Againly can inspect the local network profile, name resolution, service state, SMB configuration, and reachable endpoints, then choose the next high-information check. It can propose safe changes for review when the evidence supports them. This guide has diagnosis-level coverage, and the final proof must be opening the intended share or independently reading its availability.

Related guides: Enter network credentials keeps appearing and Network discovery is off.