NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN102 will not accept SMB/CIFS network map requests from any Windows 8.1 machine
After the recent upgrades to 6.5x, I have not been able to map the shares on my RN102. I made sure that the shares have SMB enabled and anonymous access checked. This did not happen before the upgr...
Zonker wrote:
yes I'm on 6.5.1 and can access using ReadyCLOUD. The problem is mapping the shares using Windows File Explorer.
I've seen a few of these now, and so far the solution is to add/replace credentials for the NAS in the windows credentials manager.
Try this as a test. Open CMD and enter
net use * /delete
net use t: \\nasipaddress\data /user:admin nasadminpassword
using the real ip address and admin password of course. If you aren't using the default xraid, use the real volume name instead of "data".
First command terminates any open network sessions, and if it prompts let it proceed. The second attempts to mount the NAS data volume as PC drive letter t. Let us know if that works (or how it fails).
ok missed that on the volume name and corrected it. I successfully connected to the volume, however when I disconnect and try reconnecting through file explorer it still gives me the same error. Why do I have to use the command line interface to connect to the NAS volume?
Thanks,
Zonker wrote:
Why do I have to use the command line interface to connect to the NAS volume?
You don't. It was a test to confirm that you have a credentials problem. Since using the admin credentials from the command line works, that does confirm that putting in the correct credentials in the windows credentials manager will fix it.
Credentials manager is in the control panel - open it, and delete all credentials for the NAS name and NAS IP address. Then create a new windows credential for the NAS name. You can use the admin credentials you just used for testing, or you can use another local account on the NAS.
After that is entered, confirm that it works, and create a second windows credential using the NAS IP address. That can use the same NAS username as the first credential.
StephenB wrote:Credentials manager is in the control panel - open it, and delete all credentials for the NAS name and NAS IP address. Then create a new windows credential for the NAS name. You can use the admin credentials you just used for testing, or you can use another local account on the NAS.
OK, so I did not have any entries or references to the ReadyNAS in the Windows Credential Manager. There was only references to one of my other NAS and oddly enough no reference to my WD Mybook which maps without any problems. Don't remember manually creating this entry when I set up the RN102 when it was working, so not sure how it got removed.
Anyway thanks for the help getting this sorted out.
Z
Zonker wrote:
OK, so I did not have any entries or references to the ReadyNAS in the Windows Credential Manager.
I'm glad its working now.
If there are no stored credentials, then windows uses the windows username/pass. I think something must have changed in the NAS so that the windows username/pass is now being rejected - at least that explains the change in behavior. It might be related to the new ReadyCloud accounts.
Stephen,
Thanks again for all the help. What I think is happening is that Windows is not presenting a dialog box to initially log into the volume. So without the initial login prompt, no credentials are being created for the ReadyNAS. Not sure why that would happen.
Z
Zonker wrote:
Thanks again for all the help. What I think is happening is that Windows is not presenting a dialog box to initially log into the volume. So without the initial login prompt, no credentials are being created for the ReadyNAS. Not sure why that would happen.
Again, if there are no stored credentials, windows first presents the user's windows credentials to the NAS. If that is rejected, then Windows is supposed to give the dialog box you are talking about.
That would suggest that the NAS isn't actually rejecting the user credentials, but instead is accepting them, but isn't giving the user the access they were getting before. Is the local windows account username also a local username on the NAS? Is it also a ReadyCloud account?
Is the local windows account username also a local username on the NAS? Is it also a ReadyCloud account?
Yes my Windows Login is my email address and (after the switchover to ReadyCloud in 6.5) that is the same as my ReadyCloud account. The passwords are different. Prior to this, the usernames were not the same. So I think you are on to something. Nice catch.
Z
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
