Mapped drives not accessible after PC reboot (ReadyNAS RN102)

---

dstsui wrote:
There are two accounts: Admin and David (i.e. me).

 

---

Ok.  Try the same two commands using David (with David's password).  You can't map /data that way, but you can map any share David has access to.

net use * /delete /y
net use z: \\nas-ip-address\sharename /user:David DavidPassword

If this works, then edit the two credentials to use David (with the correct password), and see if that lets you access the shares consistently.

Although it can be convenient to mount the entire data volume, it's safer to use user credentials and not admin.

---

dstsui wrote:

---

How to make the password persistent?

---

I'm not seeing that issue on my own machines.

I'm wondering if the credentials have the wrong password somehow.  That would explain the symptom (the NAS is rejecting the first access due to the wrong password, and Windows is reprompting). 

You could edit the two credentials in the Windows Credential manager (leaving the account as admin), and save the password again if you want to test this theory.

Is your user name on the computer "David", but the password is different than used for the NAS?  That can cause issues.  I had a similar problem, and found that to be the cause.  My solution was to not make the connections persistent and create a batch file that maps them, asking for the password when it does.

---

Sandshark wrote:

Is your user name on the computer "David", but the password is different than used for the NAS?  That can cause issues.  I had a similar problem, and found that to be the cause.  My solution was to not make the connections persistent and create a batch file that maps them, asking for the password when it does.

---

The name of the Windows account where it login to the NAS is not exactly David. The weird thing is that the setup is exactly the same on two existing computers and there are no problems with them . I have also removed NAS account David from Shares permission, now all of them are Anonymous, except Home Folders which has Admin permission. See image.

Can you provide commands for the batch file?

---

StephenB wrote:

---

dstsui wrote:
There are two accounts: Admin and David (i.e. me).

 

---

Ok.  Try the same two commands using David (with David's password).  You can't map /data that way, but you can map any share David has access to.

 

net use * /delete /y
net use z: \\nas-ip-address\sharename /user:David DavidPassword

If this works, then edit the two credentials to use David (with the correct password), and see if that lets you access the shares consistently.

Although it can be convenient to mount the entire data volume, it's safer to use user credentials and not admin.

---

dstsui wrote:

---

How to make the password persistent?

---

I'm not seeing that issue on my own machines.

I'm wondering if the credentials have the wrong password somehow.  That would explain the symptom (the NAS is rejecting the first access due to the wrong password, and Windows is reprompting). 

You could edit the two credentials in the Windows Credential manager (leaving the account as admin), and save the password again if you want to test this theory.

I have removed NAS account David from Shares Permissions. All Shares have just Anonymous permission except for Home Folders which has Admin permission. I have removed the credential for 192.168.1.29 and left NAS-36-1C-14 in Credential Manager because I don't want the two to create conflict. I also re-entered the password for admin in the Credential Manager. Despite all these changes, Windows still prompts for admin password. Interestingly, even if I do not provide a password and hit Cancel, the network folders which I have mapped for the Shares are accessible, it is just the network drive \\NAS\Data that fails to connect. But if the NAS fails to connect, how come the Shares are accessible?

---

dstsui wrote:
Interestingly, even if I do not provide a password and hit Cancel, the network folders which I have mapped for the Shares are accessible, it is just the network drive \\NAS\Data that fails to connect. But if the NAS fails to connect, how come the Shares are accessible?

 

---

As I said before, you can only map the entire data volume if you use the NAS admin credentials.  Also, it won't work if you are using the default admin password of "password".  If you also have a data share on the data volume, it would be best to rename it - to avoid any ambiguity.

Anonymous access has obvious security risks, especially on a business network.  Microsoft has tightened up policies for this access in Windows over the years, and that might be part of your issue.

Another aspect is that when you have no credentials for the NAS in the credential manager, then Windows will use your Windows Logon and password.  If there is a username on the NAS that matches the Windows Logon with a different password, then (a) you won't get access (even if anonymous access is allowed) and (b) you will get a password prompt.  

I recommend putting back the NAS credentials for both the IP address and the NAS name - using your NAS David account credentials. I guess you could also try setting up credentials with the username of "guest' and no password - that might also work.

---

StephenB wrote:

---

Another aspect is that when you have no credentials for the NAS in the credential manager, then Windows will use your Windows Logon and password.  If there is a username on the NAS that matches the Windows Logon with a different password, then (a) you won't get access (even if anonymous access is allowed) and (b) you will get a password prompt.  

 

Unfortunately, you won't always get a password prompt.  That's what's happening to me.  I intentionally have a different password on the NAS than in Windows but chose the same user name.  At some Windows update (I forget which), the behavior changed from prompting for another password to just failing to connect.  I've been on OS 6.9.6 (long term support) for a very long time, so it was nothing that changed on the NAS.

---

Sandshark wrote:Unfortunately, you won't always get a password prompt.  

---

Good to know.

This would be a change in Windows behavior (the NAS just denies access in this scenario).