Hi folks,
I was apprehensive about Windows 10. I know this because the upgrade icon stated for a while now that it was ready to download and install - but I wasn't. I was quite content with my Windows 7 Ultimate 64-bit OS. Unfortunately, yesterday in a particularly good mood I installed Windows 10.
This morning I found out the sound didn't work. Fixed it after half a day of tinkering. Also found out that the NAS QNAP-TS412 no longer exist under my Network section. I tried but failed to find a working solution. I'm hoping someone might have a suggestion or idea that I can try. I'm no techie by any means so please have patience and bear with me.
I tried mapping the network drive, surprisingly enough I can see in the Drive field that my folders still exist in their corresponding drive letters, but they don't show up under the NAS! When I attempt to connect them I get a Network Error message, specifically Error code: 0x80070035. The network path was not found. Windows Network Diagnostics suggested I turn on the computer or device and connect it! Haha. I have an barebone PC NUC with a LAN connection to the NAS and it read fine. No points for guessing the Windows 10 was responsible. Help!
I have attached a text file of a Speccy summary of my PC. Thanks in advance folks.
Khangster
This is a tricky one. I have been there done that as have quite a few others. There is no one size fits all answer and, as you have found, don't bother clicking the troubleshooter!
The fundamental problem being reported with that error code is that the requesting client machine issues a request to the server to display its shares but if the server does not reply, after a brief interval, the client basicly tells you the server doesn't exist (path not found). In my case, the forced Lanman server SMB protocol was wrong, hence no communication with the Lanman client service. Sometimes the Linux based NAS servers do give problems.
For starters, use the search at the top right corner of this page. '80070035 error' will do. See if any of the posts help.
Good luck.
Thanks, linw, for the tip. Perhaps if I spend a bit more time with it...
Cheers!
You could try reinstalling the QNap software.
Try Q Finder, see hereAlso, check the Windows firewall is disabled, see here
I did a Win 10 UG where the fw had enabled itself and this caused a network issue whereby my streamer couldn't see a network share
robgr my friend, you are a genius. It's fixed! I ran QNAP Finder with no luck, so I disable Windows Defender using Local Group Policy Editor, and presto! Now everything lits up like a Christmas tree.
Glad it's all working now
In my case I was using KIS 2015 which was dealing with fw duties so it didn't matter when turning of the Win fw
Are you similarly using AV software as it wouldn't be sensible to be without the fw?
If not then at least knowing it's the fw will allow you to correctly configure the fw if required
I do use KIS 2015. I haven't touch it since I totally forgot all about it! It hasn't give me a beep so I didn't even think of it...In my case I was using KIS 2015 which was dealing with fw duties so it didn't matter when turning of the Win fw
Are you similarly using AV software as it wouldn't be sensible to be without the fw?
If not then at least knowing it's the fw will allow you to correctly configure the fw if required
Since Windows update on 11/12/2015 (mess of cumulative updates) I can no longer connect to my QNAP Webdav shares. I have a HP laptop running Windows 10 Pro over wifi and am connecting using SSL.
The connections work fine after mapping them until I reboot my workstation. Then they fail consistently with the dreaded 0x80070035 error. I've set IP for NetBIOS over IP, flushed the DNS cache, I've checked hidden devices in the Device Manager for 6to4 network devices (none), turned off anti-virus and firewall, installed a new network card driver, and no change.
If I delete the mapped drives and set them up again they work fine until I reboot. I'm pulling out my last few hairs over this.
Suggestions?
John
