NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
After August 2020 W10 update ReadyNas Duo v2 will no longer automatically reconnect at logon
Up until this week we were using a perfectly good (albeit aging) ReadyNas Duo v2 which has served us well, however it has now come to light that the latest Windows 10 major update has caused issues when trying to reconnect after the PC is rebooted.
You can get around this by unmapping the drive and then re-mapping it but this is very annoying not to mention problematic for our users who are IT illiterate. Having Googled this issue it is obviously affecting many users of these older systems and wondered whetehr there's anyone out there who has a solution.
It has also affected our ability to backup the NAS to an external drive with the files now inaccessible even after the the drive is remapped.
I appreciate that at some point we need to replace this piece of kit but in a small company with limited resources there's never an ideal time and certaily not at the present with everything else going on in the world!
For reference we do have SMB 1.0/CIFS File Sharing Support enabled after encountering a similar issue after a Windows update.
Thanks in advance - Fraser
8 Replies
Since you can remap the share after the boot completes, this sounds like a timing issue in Windows. I've seen similar behavior occasionally in my PCs (long before Windows 10, and it still sometimes happens).
One option is to give your users a script that disconnects and reconnects the network drive, and just have them click on it when they have the problem.
Another option is not to map the shares to a drive letter in the first place. You can alternatively add network location(s) to file explorer, even set up desktop shortcuts. Since these are used after the user is logged in and fully connected to the network, the timing problems shouldn't be a factor.
Longer term, there are other issues you will be facing with your older NAS. It uses an outdated version of TLS - and web browsers will soon stop connecting to web servers that aren't current. There is no workaround at this point (other than to have a old browser on your system that is set not to update).
Many thanks for the prompt reply which is much appreciated.
Unfortunately 'Adding a Network location' throws up the same issue as does a desktop shortcut both of which which result in an error message basically saying that the \\NAS... files are not accessible.
As with my previous experience the only way to get around this is to re-map the drive or now, recreate the Network location.
This is definately a result of the latest Windows 10 update as I have two other PCs in the office that have not yet been updated and to all intents and purposes are the two most critical in the office which remain unnaffected, so for that I count my blessings.
For now I have delayed the update process for a maximum of the MS allowed 35 days in which time I think I'm going to have to bite the bullet and update the kit, the timing of which will be very inconvenient to say the least.
That is unless Microsoft get so many compalints they build in a temporary fix but I won't hold my breathe!
Thanks again
Fraser
Fraser-J wrote:
As with my previous experience the only way to get around this is to re-map the drive or now, recreate the Network location.
Are you using NAS user account credentials in the PC (check the Windows Credential Manager for this).
If not, you might try creating one or more NAS user accounts, and create a Windows Credential on the PC that uses them.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
