Just updated my ReadyNas RN212 firmware to 6.5.0. Have windows 10 desktop, Windows 10 Microsoft Surface and 2 x Windows 7 laptops on same network all of which could previously connect to the ReadyNas using Windows Explorer and had mapped network drives to shares. After update, access no longer possible on the Windows 10 machines either via the Readynas name (\\readynas1) or its IP address (\\192.168.2.105) and the mapped drives no longer connect. Get Windows network errors. Windows 7 laptops continue to work fine. Help please!

Just to be clear, the problem has only occured since I updated my ReadyNas to 6.5.0. Prior to that, all my PCs/laptops (combination of Windows 7 and Windows 10) could access the NAS using Windows Explorer (by it's NAS name or IP address) and had mapped drives to various shares. After the update, Windows 7 PCs are still OK but all Windows 10 ones get Network Error message ("Windows cannot access \\READYNAS1"). All machines can access the NAS via Readycloud and DLNA access to various devices I use (Smartphones, Logitech Radio, TVs etc) still works. Raidar access also still works from any PC. I log in to my Windows 10 PCs with my microsoft account the ID for which uses the same email address as I use for Readycloud but I don't see the relevance of this. Also, I had never set the Workgroup Name (in Accounts\Authentication) in the ReadyNas so it was WORKGROUP which was different to my PCs workgroup name. I've managed to regain access by doing the following:Changed the Workgroup Name in the ReadyNas to match the name used by PCs (although this did not solve the problem)Disconnected all existing mapped drivesReconnected one of the mapped drives on each Windows 10 PC using the "Connect using different credentials" tick box and using the ReadyNas admin ID and associated password.This mapped the drive but also allows me to now access the ReadyNas via Windows Explorer. Also additional drive mapping doesn't appear to require entering of the credentials.Hope this helps others who may be experiencing the same issues.

Have you checked to make sure the NAS is in the same workgroup as your Windows 10 machines? Do you login to your Windows 10 machines using your email address? If so, and if you use ReadyCLOUD is that the same email you use with that?

forestpct wrote: I log in to my Windows 10 PCs with my microsoft account the ID for which uses the same email address as I use for Readycloud but I don't see the relevance of this. That's extremely relevant as there's a known issue.

OK, thanks. Can you point me to where this known issue is documented/discussed?

forestpct wrote: OK, thanks. Can you point me to where this known issue is documented/discussed? It's documented internally. I believe we are working on a fix for a future firmware release.

Windows 10 PCs unable to access Netgear ReadyNas after 6.5.0 update

15 Replies

Replies have been turned off for this discussion

mdgm-ntgr
NETGEAR Employee Retired
May 30, 2016
Have you checked to make sure the NAS is in the same workgroup as your Windows 10 machines?

Do you login to your Windows 10 machines using your email address? If so, and if you use ReadyCLOUD is that the same email you use with that?
- forestpct
  Guide
  May 30, 2016
  Just to be clear, the problem has only occured since I updated my ReadyNas to 6.5.0. Prior to that, all my PCs/laptops (combination of Windows 7 and Windows 10) could access the NAS using Windows Explorer (by it's NAS name or IP address) and had mapped drives to various shares. After the update, Windows 7 PCs are still OK but all Windows 10 ones get Network Error message ("Windows cannot access \\READYNAS1"). All machines can access the NAS via Readycloud and DLNA access to various devices I use (Smartphones, Logitech Radio, TVs etc) still works. Raidar access also still works from any PC. I log in to my Windows 10 PCs with my microsoft account the ID for which uses the same email address as I use for Readycloud but I don't see the relevance of this. Also, I had never set the Workgroup Name (in Accounts\Authentication) in the ReadyNas so it was WORKGROUP which was different to my PCs workgroup name.
  
  I've managed to regain access by doing the following:
  Changed the Workgroup Name in the ReadyNas to match the name used by PCs (although this did not solve the problem)
  Disconnected all existing mapped drives
  Reconnected one of the mapped drives on each Windows 10 PC using the "Connect using different credentials" tick box and using the ReadyNas admin ID and associated password.
  This mapped the drive but also allows me to now access the ReadyNas via Windows Explorer. Also additional drive mapping doesn't appear to require entering of the credentials.
  Hope this helps others who may be experiencing the same issues.
  - mdgm-ntgr
    NETGEAR Employee Retired
    May 30, 2016
    forestpct wrote:
    
    I log in to my Windows 10 PCs with my microsoft account the ID for which uses the same email address as I use for Readycloud but I don't see the relevance of this.
    
    That's extremely relevant as there's a known issue.
dp12776
Aspirant
Sep 11, 2016
Solution is to turn off anti-virus.
- Jimmah
  Aspirant
  Sep 11, 2016
  On the NAS? It was never on...
  
  (edit) But! I foolishly assumed the NAS telling me it was up to date meant it would be running this fabled 6.5.2. It was, in fact, running 6.5.1 and just lying about its up-to-date nature.
  
  I'll return!
  - Jimmah
    Aspirant
    Sep 11, 2016
    Nope... 6.5.2 didn't fix it. This is a disaster.
dp12776
Aspirant
Sep 11, 2016
If it's not the anti virus then I don't know. Turning it off solved it for me.
- Jimmah
  Aspirant
  Sep 11, 2016
  Thanks anyway! I'll start a new thread.