Windows Error 0x80070035: Solutions for Network Issues

Introduction

Error 0x80070035 in Windows is accompanied by the message "Network path not found" or "The network path was not found." It occurs when attempting to access network folders, printers, or other resources on a local network. The issue can affect both home and corporate networks and is often related to network settings, services, or the firewall. In this guide, we will thoroughly examine the causes and fixes for Windows 10 and 11.

Main Causes of Error 0x80070035

Error 0x80070035 is a system code indicating a failure in resolving a network name. The main causes include:

• Network discovery disabled in the Network and Sharing Center.
• Function Discovery services are not running or have hung.
• Windows Firewall blocking traffic for network access.
• Incorrect SMB settings (e.g., SMB 1.0 disabled for older devices).
• DNS or computer name issues (name cannot be resolved).
• Duplicate computer names on the network or IP conflicts.

Method 1: Check Network Connection and Computer Name

First, ensure both computers are on the same network and can "see" each other.

1. Check physical connectivity: ensure the cable or Wi-Fi is connected and internet access is available (if required).
2. Find the target computer's name: on the target PC, open Control Panel → System and Security → System. In the "Computer name" section, copy the name.
3. Check accessibility via Command Prompt (on your computer):

   ping COMPUTER_NAME
   

   If the ping fails, check the target PC's IP address (e.g., via ipconfig) and try pinging the IP. If it works by IP but not by name, the problem is with DNS or name resolution.
4. Check for name duplication: on the target computer, ensure its name is unique on the network. If there is a conflict, change the name in the system settings.

💡 Tip: For a quick check of shared folder access, use \\IP_ADDRESS\FOLDER_NAME instead of the computer name. If that works, the issue is specifically with name resolution.

Method 2: Restart Key Network Services

The Function Discovery services are responsible for discovering network devices. If they are stopped, Windows cannot find network resources.

1. Press Win + R, type services.msc, and press Enter.
2. Find and restart the following services:
   • Function Discovery Provider Host (FDResPub)
   • Function Discovery Resource Publication (FDResPub)
   • DNS Client (Dnscache)
   • UPnP Device Host (SSDPSRV)
3. For each service: right-click → "Restart". Also check that the startup type is set to "Automatic".
4. After restarting, try connecting to the network resource again.

Method 3: Configure Windows Firewall

The firewall may block file and printer sharing. Configure the rules:

1. Open Control Panel → System and Security → Windows Defender Firewall.
2. On the left, select Allow an app or feature through Windows Defender Firewall.
3. In the list, find and enable (check the boxes) the following rules for all profiles (Private, Public, Domain):
   • File and Printer Sharing (SMB-In)
   • Network Discovery (NNTP-In, SSDP-In, UPnP-In)
4. If using a third-party antivirus with a firewall, check its settings similarly.

⚠️ Important: If the network is marked as "Public," Windows restricts sharing. In network settings (via the Network and Sharing Center), change the profile to "Private" for home networks.

Method 4: Enable Network Discovery and File Sharing

Sometimes basic sharing settings are disabled.

1. Open Network and Sharing Center (via search or ncpa.cpl).
2. Under "Network and Sharing," click Change advanced sharing settings.
3. In the "Advanced sharing settings" window, enable:
   • Turn on network discovery
   • Turn on file and printer sharing
   • You can also temporarily disable password-protected sharing for testing (not recommended for permanent use).
4. Click Save changes and restart the computer.

Method 5: Check and Configure SMB

The SMB (Server Message Block) protocol is used for file sharing. On Windows 10/11, SMB 1.0 is disabled by default due to vulnerabilities, but some older devices (e.g., NAS or printers) require it to be enabled.

1. Open Control Panel → Programs and Features → Turn Windows features on or off.
2. Find SMB 1.0/CIFS File Sharing Support.
3. If you are connecting to an older device, enable this feature. For modern systems, it is better to leave it disabled and use SMB 2.0/3.0.
4. Click OK and restart the computer.
5. If the problem persists, check that the corresponding SMB protocol is also enabled on the target computer.

Method 6: Use Command Prompt for Diagnostics and Connection

Command Prompt provides more control and helps identify the issue.

Network Diagnostics

ipconfig /all

Check that the IP address, gateway, and DNS servers are correct.

nslookup COMPUTER_NAME

Ensure the name resolves to the correct IP.

net view \\COMPUTER_NAME

Try to get a list of shared resources. If an error occurs, there is an access problem.

Force Map Network Drive

Run Command Prompt as an administrator:

net use Z: \\COMPUTER_NAME\FOLDER_NAME /persistent:yes

Replace Z: with the desired drive letter, COMPUTER_NAME, and FOLDER_NAME with actual values. If prompted for login/password, enter the credentials of the computer where the folder is located.

If the command fails with an error, check the code. For example, System error 53 is similar to 0x80070035.

Additional Tips

Registry Check (Caution!)

Sometimes changing the LMCompatibilityLevel parameter in the registry, which controls SMB security, helps. Create a restore point before editing!

1. Press Win + R, type regedit.
2. Navigate to the key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3. If the LMCompatibilityLevel parameter does not exist, create a DWORD (32-bit) value with that name.
4. Set the value to 3 (recommended for compatibility). Values:
   • 0 — send LM and NTLM (insecure)
   • 1 — send NTLM only if server agrees
   • 2 — send NTLMv2 only if server agrees
   • 3 — send NTLMv2 only (recommended)
5. Restart the computer.

If the Issue is in a Domain

When working in a domain, ensure the computer is joined to the domain and there is communication with the domain controller. Check time synchronization (command w32tm /query /status). You can also temporarily disable the firewall on the target computer for testing.

Reset Network Settings

If nothing works, reset network components:

netsh int ip reset
netsh winsock reset

Restart the computer afterward.

Quick Summary

Error 0x80070035 is usually resolved by systematically checking basic network components: ensure computers can see each other (ping), restart Function Discovery services, configure the firewall, and enable network discovery. For older devices, enabling SMB 1.0 may be necessary. If the problem persists, use Command Prompt for detailed diagnostics. Remember that in corporate networks, additional security policies may be in effect and will require coordination with an administrator.