Here is the solution to "error code 0x80070035 network path was not found" on Windows Vista and Windows 7 Computers. Click on the "START" button, select "CONTROL PANEL", and go into "DEVICE MANAGER". Click on "NETWORK ADAPTERS", then click on "VIEW", and select "SHOW HIDDEN DEVICES". In the expanded view you will see a long list of numbered "MICROSOFT 6to4 ADAPTER". My Windows 7 Professional desktop had 200 of them. Right click and select "DELETE" on all but 1 of them. You can only do 1 at a time so it does take a while. When you have only 1 left, restart computer and enjoy being able to see your other network computers, including HOMEGROUP files.
Home Network Issue: 0x80070035: Network path not found.
I'm having issues with my home network; my laptop can't access files on my HTPC
More specifically:
Both laptop and PC are running Windows 7 Ultimate. My laptop is connected to the home network wirelessly, PC is connected via LAN. Router is a Netgear DG834GV. Both computers have fixed IP addresses. They are part of the standard workgroup WORKGROUP. There used to be a Homegroup set up, which was working fine. We also have a Vista laptop which is not experiencing any unusual issues. Until a few days ago, the entire setup was working perfectly. I was previously able to access/copy/stream media, play music on the PC through Zune on my laptop, and print from my laptop to the PC, but I am now unable to do any of those. The other Laptop is still working fine.
From the Network screen on the PC I can see the laptop and access files.
However, from the network screen on the laptop, I can see the PC, but when I try to access it I get the error 'Windows could not access \MEDIACENTER. 0x80070035 The network path was not found.' I can ping the PC with both IP address and name, and I can even Remote Desktop to the PC.
ipconfig on the laptop does something funny...
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 139:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 143:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 140:
... all the way to 200. I can only assume it goes back to #1 as well.
Following some suggestions on here I just went through the enable netbios over TCP/IP but now I can't even see the PC! Can still ping it and access the internet tho.
Any suggestions as to what may be the cause?
Windows for home | Previous Windows versions | 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.
32 additional answers
Sort by: Most helpful
-
Anonymous
2017-09-08T00:40:26+00:00 I am having this issue. I am trying to access a shared folder on an old Win98 computer on our network. Win7 computers (tried 4 different ones) can access the computer in question; my Win10 laptop cannot. I tried just about every suggestion in here and have not found a solution.
Per JonKeck, I turned these on:
DNS Client (was on)
Function Discovery Resource Publication (was off)
SSDP Discovery (was on)
UPnP Device Host (was off)
I still can't access the shared folder. There is a very similar (old) computer, running Windows 95, that my Win10 laptop _can_ access.
(No jokes about old versions of Windows, please; laboratory equipment runs what it was built with.)
-
Anonymous
2014-12-30T21:25:11+00:00 I had this same issue crop up recently after years of successful file and print sharing on my home network between a Windows 7 laptop and a Vista home PC. I was pulling my hair out trying all sorts of software and setting fixes and updates and fiddling with my router since I'd changed that recently. I performed and unperformed so many changes on both systems and router that I began to doubt my understanding of simple home computing and networking.
After days of frustration and exhausting all possible router issues I began to think about what was common between the two machines and the one thing that stood out was the Virus Software, so I began to go through all of the settings of the software. I started to look at the firewall setting and what the software considered to be trusted vs restricted, and okay or not okay to run across my network. Everything looked great and I was considering shutting the software's firewall off, but as I was backing out of the firewall settings screen I noticed that the Wireless router connection had been set up as a Public Network, which must be the default since I never set this up manually in the software, and which didn't ring right with me.
Usually Public Network indicates that a whole lot of things are restricted, which I don't want hampering my own internal private network. So, I simply changed it to a Trusted Network and applied the changes. I did the same thing on my other machine and I was back in business sharing files and printers, no problemo! I wish I would have started with the firewalls instead of taking so long to get to them in my troubleshooting process. As near as I can tell it must have been either an update to my Virus software that caused the sharing functions to stop working or the removal and addition of my old and new routers that caused it. My guess is the latter.
Anyway, that's my story! Good Luck
-
Anonymous
2014-12-23T23:26:52+00:00 Try this:
How to Reinstall and reset TCP/IP for Win 7 (32 and 64):
- Click on the Start button
- Go to Accessories
- Right click on Command Prompt and select Run as Administrator
- Type netsh int ip reset c:\resetlog.txt in the Command Prompt window, and press the Enter key.
- Type winsock reset in the Command Prompt window, and then press the Enter key.
- Restart the computer.
There will be a log with the changes in c:\resetlog.txt
Hello ABA2010: You supplied this answer to "Trasvi" over four years ago, and after three months of being unable to access one Windows 7 computer from another (it worked in the other direction...) and trying every suggestion I could find, I stumbled across your post. I reset "winsock" according to your instructions, and presto - it worked! I have no idea how winsock got 'un-set" or why it all of a sudden stopped working all those months ago, but it seems to work now.
So, Merry Christmas to me, and thanks, over four years later!
Cheers,
Jim
-
Anonymous
2014-09-14T09:30:58+00:00 In my case, getting the same error code, it turned out that the Windows File and Sharing capability had been unbound from the network adapter on the target machine. Check this in Control Panel -> Network and Sharing Center -> Configure network adapters choose Advanced Settings... from the Advanced menu. Make sure that the File and Printer Sharing for Microsoft Networks binding is enabled for the relevant adapter on the target computer.