News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Troubleshooting Error 0x70080035 when accessing NAS

Started by billz, April 10, 2014, 09:47:42 AM

Previous topic - Next topic

billz

As of last weekend, I can no longer access my Buffalo Linkstation NAS from my laptop with Windows 8.1 over wifi. I upgraded to Win 8.1 several months ago and everything has been working just fine until a few weeks ago (March 23). The problem is that the NAS appears by name in the network, but when I click on it it cannot be found and I get error 0x80070035, path not found. After spending several days looking for a solution, I restored my laptop to a restore point about two weeks earlier and everything started working again. It's been working fine until this weekend (April 5), now the same problem is back.
I can browse it via its IP address, I can access the DHCP table in my router (Linksys WRT54G) and I can see the Linkstation listed there. I turned off my firewall (Symantec Endpoint) and I still get the same results. The Linkstation does show up as a media device and I can access all of my media.
Any ideas?

Texturtle

Try opening a command prompt and running ipconfig /flushdns and see if that resolves the problem.

billz

Thanks, I've tried this and no change.
It looks like my Win 8.1 laptop has a DNS problem, I can ping the NAS by IP address but not by name. This occurs whether I'm connected via wifi or plugged into my router. My Win 7 PC has no problems. I've seen quite a few posts on this subject in the Microsoft forums, but no real answers. The extremely frustrating part is that it used to work....

Net7

For all the improvements of Windows 8/8.1/8.1u1... Ya, this is a huge one!

I have had nothing but issues as well, but it works fine for all my XP/7 (and even the random Vista units i fix for people)...


Add that to the removal of managing Wireless networks with the GUI (command line is a PAIN), MicroSUCKS has managed to royally bollix networking in Windows 8+

billz

I found the problem, TCP/IP node type was incorrect. When I compared the ipconfig /all results between my working and non-working PC's, the only difference was that the node type on the non-working PC was set to Peer to Peer while the working one was set to Hybrid. I changed the node type in the registry from Peer to Peer to Hybrid and now everything works like it used to.

Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 192 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1037KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]