Map network drive from Qnap TS-431P NAS, error code 0x80070035

Hi.

I am having problems mapping my network drives in windows 10 file explorer. It is shared folders from my Qnap TS-431P NAS that I am trying to map. This has worked for about 6 months now, but suddenly it does not work any more. I have tried two different computers with the same result.

I have tried to fix this for some days now with no luck. I have a post at a official Qnap forum, but no luck there. I have also given remote access to an Qnap official but he has not been able to help me yet either. It seems like a windows issue, but I'm not sure.

The funny thing is that I can access the NAS from its web-interface or with FTP. Works just fine .. I can also access the nas from my smartphone. But I can't map the shared folders.

Here are some things I have tried after reading about the issue.

- Enable NetBIOS over TCP/IP on my network adapter TCP/IPv4 protocol

- Enable SMB 1.0/CIFS File Sharing Support under 'Turn Windows features on or off'

- Turn OFF all network discovery, un-install my network adapters under 'Device Manager' (also hidden), scan for hardware changes to re-install them and then turning network discovery back ON

- Made sure the service TCP/IP NetBIOS Helper is set to automatic/running

- In regedit Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing --> Delete the folders under MSLicensing

- Local Security Policy --> Local Policies --> Security Options --> Network security: LAN Manager authentication level --> set it to Send LM & NTLM - use NTLMv2 session security if negotiated (this was done on my win 10 pro machine)

- I have also been trying several commands in elevated powershell and CMD that I have found in different forums regarding the issue. I can't remember what it was so dont laugh at me :P (pretty much just tried everything I can find)

- Disable windows antivirus and firewall

- Enable insecure guest logons under Local Group Policy Editor --> Computer Config --> Admin Templates --> Network --> Lanman Workstation

- Added the DWORD (32bit) value AllowInsecureGuestAuth 1 under Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

When trying to map/connect to the NAS from file explorer this is what pops up (after pressing diagnose). I removed my NAS name from the screendump. I have also tried with \\[IP], same result.I can see the NAS in file-explorer under 'Network' but I can't connect to it.



When trying to map the drive from Qnap Qfinder Pro this comes up

After all the googleing and reading on forums I have done this seems like a well known issue. The only problem is that it seems there are alot of different "fixes" that work for different people. As I said, I have pretty much tried everything I have come across, but no luck yet.

Let me know what kind of logs you need. I hope someone can help :) I dont know enough about networking and windows to do this on my own.

I eventually re-initialized the NAS. Now everything works fine .. It turned out to be some sort of problem with the NAS itself, not networking/windows. Qnap ... more like Crapnap :P

Kyrre81 said:

I eventually re-initialized the NAS. Now everything works fine .. It turned out to be some sort of problem with the NAS itself, not networking/windows. Qnap ... more like Crapnap :P

Hi there

@Kyrre81

Góðan dag !!

Glad you fixed it -- but I agree QNAP Crapnap.

I find something like those small micro cube HP ProLiant GEN8 / GEN 10 microservers with a decent standard Linux Distro (recommend CENTOS / SUSE / UBUNTU ) infinitely better and cheaper for running a NAS than proprietary (and usually more expensive boxes like QNAP).

Those 3 distros will work straight out of the box - you don't need a mega powerful CPU for a NAS - Internet / LAN connection more important plus DECENT reliable disks . You can use other distros like MINT as well but the 3 I've given are 100% stable and ideal for running things like servers.

Just start samba - and you've got access to your files --simple !!!!!

here's 2 NAS boxes 1 HP gen 8 microserver and 1 HP gen 10 Microserver bog standard SAMBA and SATA HDD's



The Microservers are really cheap - especially if you have your own HDD's - these servers are quite small - could even be a box under your main remote TV - and not noisy - and have 4 Bays for HDD's. Easily swappable (Not hot swappable though) with USB3 / USB2 connections and 2 Ethernet ports.

I don't like the closed nature of QNAP - plus with a decent Linux distro it makes installing software a breeze. Simply ensure SAMBA is up and running and Linux Networking tends to work first time --Windows is always a bit of hit and miss.

Another advantage of the Linux solution is that you can use the software RAID (mdadm) which is far better than the usually fairly poor cheap hardware RAID implemented on a lot of NAS type boxes -- if you can boot into standard AHCI mode I.e turn Hardware RAID off and use Software RAID you'll improve the I/O on that box about a zillion times !!!! plus HDD's can be all sorts of varying sizes too with the Linux mdadm solution.

Cheers
jimbo

jimbo45 said:

I have had different types of "server" through the years. The reason why I got this NAS was that a wanted a simple stand-alone unit "that just works", making it easy for all in the household to store data there from PC's, smartphones etc.
But it seems it causes headache ... And (i think) it has gotten worse since v1607 of Windows 10.

Like I mentioned when marking this thread as 'solved' .. the NAS works now. However it seems I have to remap the shared folders from the Qnap software EVERY TIME i restart the PC. Grrr!! Neverending pile of sh***

I can get a HP E Proliant Microserver Gen 10 Entry for about 478 USD. (Edit: Or 49400 ISK. (really? Whats up with your currency?)) I have the disks. Maybe I can sell the NAS and cover some of this.
I would have to think about that. The NAS has worked just fine, and its working now .. really only the re-map issue left solving.