Share via

Network Path Not Found

Anonymous
2025-01-12T20:31:22+00:00

I recently tried to repurpose a old PC to make a "storage server" to backup important documents on my private network with a fresh Win11 Home install.

I had everything setup and my gaming PC (win11 Home) can easily connect and transfer files to said computer.

My problem is I have another computer that is also Win11 Home that CANNOT connect without getting the error code "Network Path Not Found: Error Code 0x00870035". It is setup the same exact way as my gaming PC that connects fine.

I have spent probably 2 days going through various posts, forums and videos trying to figure this out and basically tried everything from resetting network adapter, resetting network permissions, resetting the share settings on the host PC, screwing around with SMBv1 or SMBv2 settings, updating drivers, disabled firewall, enabled NetBios. All PCs are connected via hardline.

Windows for home | Windows 11 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-18T14:09:47+00:00

    None of these solutions worked. I can ping the server PC from both PCs and no issues, subnets are correct. I put a network card into both the PC that can not connect and the server PC with no luck. I reinstalled Windows on both PCs that can not connect and made new Window Users Profile.

    Problem still persists, these two PCs just can't communicate to access a simple folder. While my other PC connects to each just fine. At this point I have spent over 5 days trouble shooting between these suggestions and various others from around the web, spent money on after market network cards to rule that out. Hell I even bought new ethernet cables as a hail mary. At this point I am done and will probably look to a third party software or non windows products.

    Thanks for trying.

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-13T07:05:48+00:00

    Hello MitchLB606,

    Welcome to the Microsoft Community.

    The "Network Path Not Found: Error Code 0x00870035" error you're encountering typically points to a networking or sharing issue between devices in a local network. Given that your gaming PC is working fine while the other one isn't, this suggests that the issue may lie with the configuration of the problematic PC, network settings, or firewall settings.

    Here’s a structured approach to resolving the issue:

    1. Verify Network Configuration

    • IP Address Conflicts: Ensure that all PCs on your network are in the same subnet. If the IP addresses are on different subnets, the devices won't be able to communicate properly.
      • On the problematic PC, open Command Prompt and type ipconfig to check the IP address.
      • Ensure that the IP address of the problematic PC is within the same network range as your other devices (e.g., if your other PCs have an IP like 192.168.1.x, the problematic PC should have a similar IP like 192.168.1.x).
    • Ping Test: From the problematic PC, try pinging the storage server PC:
        ping <IP-of-storage-server-PC>
      

    If the ping fails, there might be a deeper network issue like a misconfigured IP or subnet.

    2. Ensure File and Printer Sharing is Enabled

    • On the problematic PC, go to Control Panel > Network and Sharing Center > Change advanced sharing settings.
    • Ensure the following options are enabled:
      • Turn on network discovery.
      • Turn on file and printer sharing.
      • Allow Windows to manage homegroup connections (if you're using HomeGroup).

    3. Check SMB Settings

    • SMBv1, SMBv2, and SMBv3: Windows 11 generally uses SMBv2 or SMBv3 for file sharing. If you’ve disabled SMBv1 for security reasons, ensure SMBv2 or SMBv3 is enabled.
      • Open Control Panel > Programs and Features > Turn Windows features on or off.
      • Ensure SMB 1.0/CIFS File Sharing Support is checked if necessary (though this is typically not recommended for security reasons, especially for modern setups).
      • Also, ensure SMB Direct is enabled for SMBv3.
      • Run the following command to ensure SMBv2 is active:
          Get-SmbServerConfiguration | Select EnableSMB2Protocol
        

    4. Check DNS and Name Resolution

    • DNS Issues: Ensure that the problematic PC can resolve the network name of the storage server.
      • Try to access the server by IP address rather than hostname:
          \\<IP-of-storage-server-PC>
        
    • If the above works but using the computer name doesn't, it might be a DNS or NetBIOS issue.
    • You can enable NetBIOS over TCP/IP on both PCs:
      • Open Control Panel > Network and Sharing Center > Change adapter settings.
      • Right-click your network adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) > Advanced > WINS tab.
      • Enable NetBIOS over TCP/IP.

    5. Disable/Configure Firewall

    • While you’ve mentioned disabling the firewall, ensure that the proper ports for file sharing are open and not being blocked.
      • Open Windows Defender Firewall > Advanced settings > Inbound Rules.
      • Look for rules related to File and Printer Sharing (UDP 137-139, TCP 445) and ensure they are enabled.
      • Alternatively, temporarily turn off the firewall entirely to rule it out as the issue:
        • Open Control Panel > Windows Defender Firewall > Turn Windows Defender Firewall on or off.
        • Select Turn off Windows Defender Firewall for both private and public networks.
      • If disabling the firewall resolves the issue, you may need to create custom rules for file sharing in the firewall.
    • Disclaimer: Temporarily turn off antivirus protection. However, keep in mind that if you do so, your device may be vulnerable to threats. So please turn it on immediately once issue fixed.

    6. Verify Workgroup Settings

    • All the PCs need to be in the same workgroup. You can check and set the workgroup name by:
      • Right-click This PC > Properties > Advanced system settings > Computer Name tab.
      • Ensure all PCs are in the same workgroup (default is usually WORKGROUP).

    7. Map the Network Drive Manually

    • Try mapping the network drive manually on the problematic PC:
      • Open File Explorer > This PC > Map network drive.
      • In the "Folder" field, enter the storage server’s path (e.g., \<StorageServer-IP>\SharedFolder).
      • Ensure you use the proper credentials if needed.

    8. Check for Windows Updates

    • Ensure all your PCs, especially the problematic one, have the latest updates installed.
      • Go to Settings > Update & Security > Windows Update and install any pending updates.

    9. Try Using a Static IP on the Storage Server

    • If the storage server is using DHCP, there’s a chance the IP address changes over time, causing connectivity issues. Assign a static IP to the storage server to ensure consistent access.

    10. Check Network Adapter Settings

    • Try resetting the network adapter on the problematic PC:
      • Go to Device Manager > Network adapters, right-click on your network adapter, and select Uninstall.
      • After uninstalling, restart the PC and Windows will automatically reinstall the network driver.
    • Additionally, ensure that the network adapter is set to use the correct settings (e.g., IPv4).

    11. Test in Safe Mode with Networking

    • Boot the problematic PC in Safe Mode with Networking to see if any third-party software or settings are causing the issue.
      • Restart your PC, press F8 during boot, and select Safe Mode with Networking.
      • Test if the connection works in this mode.

    By systematically working through these steps, you should be able to resolve the "Network Path Not Found" issue on the problematic PC. If the problem persists, consider checking for any hardware-specific network issues, or test with a fresh Windows user profile to rule out profile-specific configurations.

    Best Regards,

    William.Y | Microsoft Community Support Specialist

    1 person found this answer helpful.
    0 comments No comments