[SOLVED] Error code 0x80070035 - The network path is not found

axw

Distinguished
Sep 27, 2013
18
0
18,520
1
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)
3.LROOM-PC (WIFI)

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
Here is my diagram and error 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:

Verify SMB 1.0/CIFS File Sharing Support is Installed - Enable/disable SMB V1.0
Disable the Internet Protocol Version 6
Network Reset - ipconfig /release ipconfig /flushdns ipconfig /renew - Reset TCP/IP
Enable LanMan Workstation
Static/Dynamic IPs
Make sure sharing is enabled on the folder
Using gpedit.msc - Enable insecure guest logons (regedit also)
Disable the antivirus and Firewall temporarily
Reinstall network adapter on MAIN-PC
Enable NetBIOS over TCP/IP
Modify the Network Security settings - Local Policies >> Security Options - Send LM & NTLM-use NTLMv2 session security if negotiated
Installed Reliable Multicast Protocol
Connect to the target computer using IP - fail
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]
Permissions (security and share) on MEDIA-PC set to Everyone
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.
 

axw

Distinguished
Sep 27, 2013
18
0
18,520
1
Found resolution on another forum.
When trying to ping using a hostname I was getting
Ping statistics for ...:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Reply from ...: Destination host unreachable.

The returning IP was the gateway IP.

The culprit was the hosts file that had one line pointing the wrong IP to the MEDIA-PC.
Removed the line and now everything works.

Thank you everyone for the tips.
 

Ralston18

Titan
Moderator
Check MEDIA-PC: If it was just upgraded to WIN10 take a look at the Homegroup. Compare the configuration to the computers that do have two way access.

============

MEDIA-PC and MAIN-PC are both using Ethernet cable connections to the switch - correct?

Have you tried swapping in known working Ethernet cables?

=====

Make and model information for Router and Switch?

The router's logs (if available and enabled) may be capturing some error message.
 

axw

Distinguished
Sep 27, 2013
18
0
18,520
1
Check MEDIA-PC: If it was just upgraded to WIN10 take a look at the Homegroup. Compare the configuration to the computers that do have two way access.
Did it multiple times, everything is the same.
WIN 10 is a clean install

MEDIA-PC and MAIN-PC are both using Ethernet cable connections to the switch - correct?

Have you tried swapping in known working Ethernet cables?
Yes, just recently the switch has been installed and the new router, issue persists before and after these changes.

Make and model information for Router and Switch?

The router's logs (if available and enabled) may be capturing some error message.
No error or alarm messages in the log related to the computers ID
 

Ralston18

Titan
Moderator
Windows 10 - Clean installs noted.

However, my thought being that some default setting is still in place and getting in the way of the share between the two computers.

Take as close of a look as you can to compare a fully working share (both ways) with the share (MEDIA and MAIN) that is working only one way.

"Network Path not found".

Try "pathping" and "tracert" between the two computers.

Also run "arp -a" on all three computers. Determine if the MACs (Physical Addresses) are correct.

Lastly try "net view".

Do you get any error messages? Especially regarding protocols?
 

axw

Distinguished
Sep 27, 2013
18
0
18,520
1
Windows 10 - Clean installs noted.

However, my thought being that some default setting is still in place and getting in the way of the share between the two computers.

Take as close of a look as you can to compare a fully working share (both ways) with the share (MEDIA and MAIN) that is working only one way.

"Network Path not found".

Try "pathping" and "tracert" between the two computers.

Also run "arp -a" on all three computers. Determine if the MACs (Physical Addresses) are correct.

Lastly try "net view".

Do you get any error messages? Especially regarding protocols?
I'll try this and let you know.
 

axw

Distinguished
Sep 27, 2013
18
0
18,520
1
Found resolution on another forum.
When trying to ping using a hostname I was getting
Ping statistics for ...:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Reply from ...: Destination host unreachable.

The returning IP was the gateway IP.

The culprit was the hosts file that had one line pointing the wrong IP to the MEDIA-PC.
Removed the line and now everything works.

Thank you everyone for the tips.
 

ASK THE COMMUNITY