Tuesday, 24 April 2018

Windows cannot access Network Drive


We have a network drive and media Server at Lamas HQ and I have had some issues recently trying to access it through File Manager.

This is the error message:


I spoke to the Network Manager several times.  He always suggested rebooting my pc or rebooting the router.  Now this sometimes worked.  Other times it was just an exercise in futility ending in me getting extremely frustrated with things and not being able to access anything on the network.

We had a new QNAP server installed earlier in the year and we blamed it on that to some extent.  However, it was getting more and more frequent and more difficult to resolve.

All the Lamas HQ equipment is running Windows 10 fully up to date, patched and fully AV protected.

Turns out that was the reason for the failure to connect!

I did a Google Search on the error and found this explanation on the QNAP site.

The SMB v1 application that was available prior to the 1709 update, is now not available after the update and that is what is effectively, preventing connection through Windows File Manager.

The answer is to map the drive in File Manager and there should be no further issue.

Click on ThisPC in File manager and there are 2 options

The option Map the Network Drive does just that. The folder you specify is the one that it goes to.



In the example above if you were to map the Company Directory you will be able to see that drive and its content but not the Films or other same level directories.

You will be able to map the different top level directories but  each one will need to be done separately.

The other way to do it is to Add a Network Location.


Follow the onscreen directions and then you will be able to pin this to the quick menu.  This will however allow you to see the whole network drive and not just the mapped drive.



No comments:

Post a Comment

Windows 10 - May 2019 update - remove USBs

So the Laptop... I tried several times to update to 1903 and every time i had the same result.   I tried updating from Windows Upd...