Windows 10 won't access shares on one computer

JennC: Thank you for the suggestion. Unfortunately, implementing your recommendation had no effect. I have not had an opportunity prior to this to test your proposal before this.

JennC wrote:

---

Is the computer that gets trouble accessing the NAS via ReadyNAS Remote connected to the same LAN where the NAS is? Can you check if that computer can access the shares locally?

 

The failures occur when I am using ReadyNAS Remote to from outside the local network of the NAS. The computer can access the NAS just fine when it's on the same local network. In this case, though, I'm not using ReadyNAS Remote.

I found a post with similar problem reported that I consider a partial success:

https://community.netgear.com/t5/Legacy-NETGEAR-and-Partners-Add/Windows-10-won-t-access-shares/m-p/1148058#M14492

Here's how I implemented the referenced solution:

- Launch the "Credential Manager" in Windows 10 (type "credentials" in the Cortana search bar)

- Select "Credential Manager" from the search results
- Click "Windows Credentials"
- Click "Add a Windows credential"
- Internet or Network Address: IP address of ReadyNAS remote relay*
- User name: Local UserName for the NAS
- Password: PW for the local UserName

* The IP address for what I'm calling the ReadyNAS remote relay can be obtained by:

1) Right-click on the ReadyNAS remote icon in the system tray and

2) Click "Show Device from the resulting menu

3) Click "Copy IP"  and then paste into the proper field of the new Windows Credential being set up.

While the solution provided above worked for me, it's not ideal because there is no longer a login prompt to access the nas; ReadyNAS Remote logs me in automatically at the NAS level. For my files I prefer the additional security provided by a login requirement. So, while this is an acceptable workaround at pesent, I'm still hoping I can find a solution that retains the NAS login requirement.

Additional suggestions are appreciated.