NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Windows 10 won't access shares on one computer
I have a netgear ReadyNas Ultra 4 which I access remotely using ReadyNAS Remote on two computers - both running Windows 10 Pro version 1607 Build 14393.222 & ReadyNAS Remote (Version 1.7.6.28) . I ...
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:
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.
Hello AnnoyedUser,
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?
Try also the following:
1. Go to Control Panel. Then Network Connections
2. Choose Advanced from the top menu bar.
3. Then Advanced Settings.
4. Under the Adapters and Binding, you will see a section for Connections.
5. Move the Leaf Networks Adapter to the bottom of the list.
Welcome to the community!
Regards,
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:
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.
AnnoyedUser wrote:
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.
Windows is automatically logging in using the credential you entered (not Remote).
If you set the password in the credential to blank, do you get a logon prompt?
StephenB wrote:Windows is automatically logging in using the credential you entered (not Remote).
If you set the password in the credential to blank, do you get a logon prompt?
Yes, indeed!
Great suggestion.
The UserName is still automatically populated, which is still not ideal from a security standpoint, but it is a tremendous improvement.
Thank you!
I'm still curious what might have prompted this behavior. As I mentioned, I have not experienced this on my other computer.
AnnoyedUser wrote:
I'm still curious what might have prompted this behavior. As I mentioned, I have not experienced this on my other computer.
It is a bit puzzling to me also, and there are a lot of users over the past couple months who have needed to set up credentials.
I am guessing it is some change in windows 10. Do your two windows machines both use local accounts? Are the usernames for the PCs structured differently (one email-format perhaps)?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
