Solved Network path not found error 0x80070035

[DanielMacy]

I have three systems on a home network: one running XP, one running Win 7 32-bit, and the other running Win 7 64-bit.

From the XP system, I can see the 32-bit Win 7 system and vice versa. But neither one can see the Win 7 64-bit system. On XP, I get the error: \\Win764System is not accessible. On the Win 7 32-bit system, I get the 0x80070035 error: The network path was not found.

On the Win 7 64-bit system, I get the 0x80070035 error when I try to navigate to either of the other two systems.

I have tried "Enable NetBIOS over TCP/IP" in the TCP/IPv4 properties. I have tried "Send LM & NTLM - use NTLMv2 session security if negotiated" in Local Security Policy. Nothing changes the behavior of the Win 7 64-bit system.

I have also tried disabling the Windows Firewall without success.

I have avast antivirus installed and tried stopping all of the real-time shields, but nothing changed the behavior.

Any other ideas? Thanks!

 

[Ztruker]

Do the following from both Windows 7 systems so we can compare them.

Click on Start then Run or press Window key (next to left Ctrl key) +R and paste the following into the Run box, exactly as shown, including double quotes:

cmd /c "ipconfig /all > postme.txt & ping yahoo.com >> postme.txt & notepad postme.txt & del postme.txt"

and press ENTER.

A file will open in Notepad. Please copy and paste the contents here. Close the Notepad window and the file will be deleted and the Command Prompt window will also close.

If you don't have a Run selection off the Start menu, see here: Enable Run Command on Windows 7 or Vista Start Menu

 

[DanielMacy]

When I ran the command on the 64-bit system, it couldn't find ipconfig, so there's no ipconfig output. Here's what it gave me:

Pinging yahoo.com [72.30.38.140] with 32 bytes of data:
Reply from 72.30.38.140: bytes=32 time=106ms TTL=49
Reply from 72.30.38.140: bytes=32 time=74ms TTL=49
Reply from 72.30.38.140: bytes=32 time=110ms TTL=49
Reply from 72.30.38.140: bytes=32 time=76ms TTL=49

Ping statistics for 72.30.38.140:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 110ms, Average = 91ms

Here's the output from the 32-bit Win 7 system:

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC30
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller #2
Physical Address. . . . . . . . . : 00-21-9B-16-8E-8A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c57a:3e2:51e2:f6d9%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, August 13, 2012 1:32:31 PM
Lease Expires . . . . . . . . . . : Monday, August 20, 2012 1:32:31 PM
Default Gateway . . . . . . . . . : 192.168.1.100
DHCP Server . . . . . . . . . . . : 192.168.1.100
DHCPv6 IAID . . . . . . . . . . . : 285221275
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-87-50-E8-00-21-9B-16-8E-8A
DNS Servers . . . . . . . . . . . : 192.168.1.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 7A-79-05-AE-B7-D8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2620:9b::5ae:b7d8(Preferred)
Link-local IPv6 Address . . . . . : fe80::f464:76eb:d5d5:e87e%18(Preferred)
IPv4 Address. . . . . . . . . . . : 5.174.183.216(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Lease Obtained. . . . . . . . . . : Monday, August 13, 2012 9:21:33 AM
Lease Expires . . . . . . . . . . : Tuesday, August 13, 2013 9:23:40 AM
Default Gateway . . . . . . . . . : 5.0.0.1
DHCP Server . . . . . . . . . . . : 5.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 410679632
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-87-50-E8-00-21-9B-16-8E-8A
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{A102F17B-014A-4B5E-A528-FBD38CAC9B84}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2428:eb8:38e1:9d31(Preferred)
Link-local IPv6 Address . . . . . : fe80::2428:eb8:38e1:9d31%12(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{B70EDB06-8FC2-41BA-A845-898AD5D50FA4}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Pinging yahoo.com [72.30.38.140] with 32 bytes of data:
Reply from 72.30.38.140: bytes=32 time=126ms TTL=49
Reply from 72.30.38.140: bytes=32 time=83ms TTL=49
Reply from 72.30.38.140: bytes=32 time=69ms TTL=49
Reply from 72.30.38.140: bytes=32 time=76ms TTL=49

Ping statistics for 72.30.38.140:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 126ms, Average = 88ms

Dan

 

[DanielMacy]

I don't know what I did wrong the previous time, but I was able to get ipconfig output from the 64-bit Win 7 system:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DAN-LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
Physical Address. . . . . . . . . : 8C-70-5A-B8-45-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 8C-70-5A-B8-45-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205
Physical Address. . . . . . . . . : 8C-70-5A-B8-45-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9880:7baa:cf59:c307%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, August 13, 2012 3:48:31 PM
Lease Expires . . . . . . . . . . : Monday, August 20, 2012 3:48:31 PM
Default Gateway . . . . . . . . . : 192.168.1.100
DHCP Server . . . . . . . . . . . : 192.168.1.100
DHCPv6 IAID . . . . . . . . . . . : 227307610
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-7A-44-68-D4-BE-D9-40-65-EE
DNS Servers . . . . . . . . . . . : 192.168.1.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : D4-BE-D9-40-65-EE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 7A-79-05-CA-CD-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2620:9b::5ca:cd01(Preferred)
Link-local IPv6 Address . . . . . : fe80::fc25:d748:dae5:f6a6%18(Preferred)
IPv4 Address. . . . . . . . . . . : 5.202.205.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Lease Obtained. . . . . . . . . . : Monday, August 13, 2012 3:48:05 PM
Lease Expires . . . . . . . . . . : Tuesday, August 13, 2013 3:50:12 PM
Default Gateway . . . . . . . . . : 5.0.0.1
DHCP Server . . . . . . . . . . . : 5.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 763001138
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-7A-44-68-D4-BE-D9-40-65-EE
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:183a:825:38e1:9d31(Preferred)
Link-local IPv6 Address . . . . . : fe80::183a:825:38e1:9d31%16(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{F81000DD-AEC8-4EB1-B9B0-1B688B798564}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{9AEE3823-AA18-4B71-8599-61860CDCFD8B}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Pinging yahoo.com [72.30.38.140] with 32 bytes of data:
Reply from 72.30.38.140: bytes=32 time=145ms TTL=49
Reply from 72.30.38.140: bytes=32 time=405ms TTL=49
Reply from 72.30.38.140: bytes=32 time=265ms TTL=49
Reply from 72.30.38.140: bytes=32 time=239ms TTL=49

Ping statistics for 72.30.38.140:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 405ms, Average = 263ms

Dan

 

[DanielMacy]

I should add that when I am in Windows Explorer, if I enter the IP address in the address bar, it finds that system and I can navigate to it. If I click on a system name under "Network" in the left pane of Windows Explorer, that's when I get the error that the network path cannot be found. It seems that it has a problem with the name resolution, but I have no idea how to fix it.

 

[chev65]

The Hamachi interface has been causing similar problems on Windows 7 recently. You might try disabling Hamachi and the Microsoft virtual wifil miniport adaptors.

 

[DanielMacy]

I can disable Hamachi and the wifi miniport adaptors, but I'm not sure how to test whether it solves my problem. Even with Hamachi enabled, I can navigate to the systems I want using their IP addresses. With Hamachi disabled, the only way I know to get to a different system is with its IP address, but that's what I'm trying to avoid having to use.

It's when I click on the name of the system in the Network list in Windows Explorer that Windows tells me that there is a network path error.

 

[chev65]

I can disable Hamachi and the wifi miniport adaptors, but I'm not sure how to test whether it solves my problem. Even with Hamachi enabled, I can navigate to the systems I want using their IP addresses. With Hamachi disabled, the only way I know to get to a different system is with its IP address, but that's what I'm trying to avoid having to use.

It's when I click on the name of the system in the Network list in Windows Explorer that Windows tells me that there is a network path error.

Assuming that all these machines are in the same network and using the same workgroup name with the appropriate permissions you should have no problems accessing them.

It may help to go into the sharing and the security tabs on the 64 but machine's C drive, advanced sharing, "type in" "everyone" on both tabs, then use the check marks for access levels as desired.

 

[DanielMacy]

They're not all in the same network. There are three systems in my network at home that I mentioned in my initial post. They are in the same network and workgroup. I also have some systems at my company's home office that I'm trying to access; they are not necessarily in the same workgroup. They are all showing up in Hamachi with green lights beside them, and they all list under Network in Windows Explorer. It's when I click on them in Windows Explorer that I get the error. And I get the same error when I try to click on the name of another system in my home network.

It seems to be a name resolution issue--that it can't figure out the IP address of a system that's listed by name so that it can navigate to it.

Also, it is only a problem on my laptop that is running the 64-bit version of Windows 7. It was brand new about a month ago.

 

[chev65]

They're not all in the same network. There are three systems in my network at home that I mentioned in my initial post. They are in the same network and workgroup. I also have some systems at my company's home office that I'm trying to access; they are not necessarily in the same workgroup. They are all showing up in Hamachi with green lights beside them, and they all list under Network in Windows Explorer. It's when I click on them in Windows Explorer that I get the error. And I get the same error when I try to click on the name of another system in my home network.

It seems to be a name resolution issue--that it can't figure out the IP address of a system that's listed by name so that it can navigate to it.

Also, it is only a problem on my laptop that is running the 64-bit version of Windows 7. It was brand new about a month ago.

Oh ok, didn't realize it was another network you were accessing using the Hamachi interface.

From what I have read about this problem it can be many things causing it so it's hard to diagnose precisely. The link below shows quite a few ways to resolve this problem but I have no idea which one might apply.

Home Network Issue: 0x80070035: Network path not found. - Microsoft Answers

 

[DanielMacy]

I tried a clean boot with all non-Microsoft services turned off except for Hamachi, and I still have the problem. I've decided to give up for now, and instead I'm going to use the mapped network drive feature of Windows Explorer for the few systems that I need to connect to regularly.