Billy Xiong Asserted: Error code 0x80070035 – The network path is not found

Windows 10 machine can't connect to network drive - is home...

I’m looking for a kind soul who can help me resolve this long standing issue with my network that has been driving me insane.

I have set up many home networks, resolved many issues but I seem to be stuck at this one.


I have 3 computers in my home network:

  1. MAIN-PC (Ethernet)
  2. MEDIA-PC (Ethernet)


All computers can see each other, all computers can access each other except the most important one,

from 1.MAIN-PC to 2.MEDIA-PC (they can ping each other)


I get this error code 0x80070035

The network path is not found


Diagram attached to get a better understanding.




All of the computers have installed:

Windows 10 Pro 64-bit

Version: 10.0.19042 Build 19042

MBOs not older than 2 yrs.


I have tried following things:


  1. Verify SMB 1.0/CIFS File Sharing Support is Installed – Enable/disable SMB V1.0
  2. Disable the Internet Protocol Version 6
  3. Network Reset – ipconfig /release ipconfig /flushdns ipconfig /renew – Reset TCP/IP
  4. Enable LanMan Workstation
  5. Static/Dynamic IPs
  6. Make sure sharing is enabled on the folder
  7. Using gpedit.msc – Enable insecure guest logons (regedit also)
  8. Disable the antivirus and Firewall temporarily
  9. Reinstall network adapter on MAIN-PC
  10. Enable NetBIOS over TCP/IP
  11. Modify the Network Security settings –  Local Policies >> Security Options – Send LM & NTLM-use NTLMv2 session security if negotiated
  12. Installed Reliable Multicast Protocol
  13. Connect to the target computer using IP – fail
  14. Windows Firewall > incoming > file and printer sharing (smb incoming) [choose the one with the green bubble for your active profile] > area > remote-ip [add the ip-range of your vpn-network here]
  15. Permissions (security and share) on MEDIA-PC set to Everyone
  16. Enable all Network services


MEDIA-PC had WIN7 installed and this issue was present then.

I changed the MBO on the MEDIA-PC recently and installed WIN10 PRO (not for this reason, upgrade) I hoped the problem would be resolved but interestingly enough it was not. That probably means the issue is on my MAIN-PC.

Edited by motoMoto, Today, 04:27 PM.

Billy Xiong

Author: Billy Xiong

Leave a Reply

Your email address will not be published. Required fields are marked *