NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Fraser-J
Aug 28, 2020Aspirant
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 w...
StephenB
Aug 28, 2020Guru - Experienced User
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).
- Fraser-JAug 28, 2020Aspirant
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
- StephenBAug 28, 2020Guru - Experienced User
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.
- Fraser-JAug 28, 2020Aspirant
Hi, yes I am using NAS user account credentials on the relevant PCs so there's nothing I can do there.
At the end of the day I think that I don't have much choice but to upgrade the NAS. To that end I'am currently looking at a ReadyNAS 424 that I'll fill with 1TB Samsung SSDs which should last for the foreseeable future and leave me to get on with more productive work : )
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!