ReadyNAS 102 user login failure to Home folder

Question

Greetings, we have 2 ReadyNAS 102, one of them is from 2014, the other from 2016 and they´re still going strong!

However, the newer one had recently disk failure (RAID-1 and also almost full volumes), so last weekend we upgraded it with 2 new 4TB disks (500GB before) and followed the instructions to replace faulty drive first, let it spool the data, and then replaced the other disk. All this went extremely well, I´m impressed that these small devices supports HotSwap and growing volumes on the fly. Good job!

We also upgraded firmware to 6.10.7 before the disk swaps.

But... after we did this, the user (there´s only one user) cannot login to her Home folder from her Laptop (Windows 11). She get´s "wrong password". All other shared folders with their files (/Videos, /Pictures, /Documents) are accessible. We can see her Home folder (/julia) in Windows Explorer under Network. We have also tried to change her password on the ReadyNas, but still gets "permission denied" or "wrong password".

I think it might be Windows that for some reason have cached her previous credentials, could that be the case?

I just looked in the smbd.log from yesterday when we tried (again) to fix this, and we do see logs that says "wrong password":

[2022/09/20 15:41:50.396399, 2] ../source3/auth/auth.c:332(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [julia] -> [julia] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2022/09/20 15:45:29.756249, 2] ../source3/auth/auth.c:332(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [julia] -> [julia] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2022/09/20 15:45:29.923435, 2] ../source3/auth/auth.c:332(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [julia] -> [julia] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2022/09/20 15:45:33.240832, 2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
check_ntlm_password: authentication for user [julia] -> [julia] -> [julia] succeeded
[2022/09/20 16:06:38.572655, 2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
check_ntlm_password: authentication for user [julia] -> [julia] -> [julia] succeeded
[2022/09/20 16:06:58.439081, 2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
check_ntlm_password: authentication for user [julia] -> [julia] -> [julia] succeeded
[2022/09/20 16:07:19.289638, 2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
check_ntlm_password: authentication for user [julia] -> [julia] -> [julia] succeeded
[2022/09/20 16:08:50.160127, 2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
check_ntlm_password: authentication for user [pelle] -> [pelle] -> [pelle] succeeded
[2022/09/20 21:06:03.195284, 2] ../source3/auth/auth.c:332(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [julia] -> [julia] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2022/09/20 21:06:03.324968, 2] ../source3/auth/auth.c:332(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [julia] -> [julia] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1

I´m out of ideas.. 😞

Before the disk upgrade - no problems with Home folder access.

Oh, we did one extra thing during disk upgrade - I renamed the ReadyNas hostname because previous hostname had an underscore in it, so we changed hostname from My_Nas --> My-Nas. I dont´t see that this could cause the problems we have now, but anyway...

What have we missed?

StephenB · Answer

pellelon&nbsp;wrote:&nbsp;Oh, we did one extra thing during disk upgrade - I renamed the ReadyNas hostname because&nbsp;previous hostname had an underscore in it, so we changed hostname from My_Nas --&gt; My-Nas. I dont´t see that this could cause the problems we have now, but anyway...
&nbsp;
What have we missed?
&nbsp;

Her password was likely saved in the windows credentials manager - but that credential now won't be applied because you changed the hostname.
&nbsp;
Note that if there is no credential stored in the credential manager, then Windows will use the Windows username+password.&nbsp; I'm thinking that is what happened here (that julia is the windows username as well, and that the windows password is not the same as the one in the NAS).
&nbsp;
You can go into the credential manager, delete the old credential, and create a new one. Another option is to make sure the password for the NAS user account matches her windows password.

pellelon · Answer

Yes, that was my thoughts too. I know that when we changed password on the ReadyNas, that would differ from her Windows (julia) login.

But you´re supposed in Windows to click that box "use other credentials" when doing "Map Network Drive".

So even when we do that and type both user (julia) and the ReadyNas passwd Windows complains...

Oh, one other strange thing in the log from ReadyNas above: You see that "some" logins from "julia" is successful! We heven´t figured out what logins that is ok. Could it be that ReadyNas logs successful "logins" even if you access the shared folders that anyone can access...?

I don´t know how to alter Window credentials, so if anyone has link to description on how to do that, I would be glad!

StephenB · Answer

pellelon&nbsp;wrote:
&nbsp;
I don´t know how to alter Window credentials, so if anyone has link to description on how to do that, I would be glad!
&nbsp;

https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0
&nbsp;
pellelon&nbsp;wrote:
&nbsp;
Oh, one other strange thing in the log from ReadyNas above: You see that "some" logins from "julia" is successful!

Is it possible that she is sometimes accessing the NAS using its IP address, but using the hostname other times?
&nbsp;
Windows treats the IP address and hostname as different machines (and they can have different credentials in the credential manager).
&nbsp;
pellelon&nbsp;wrote:
&nbsp;
Oh, one other strange thing in the log from ReadyNas above: You see that "some" logins from "julia" is successful! We heven´t figured out what logins that is ok. Could it be that ReadyNas logs successful "logins" even if you access the shared folders that anyone can access...?
&nbsp;

If the username matches one with a NAS user account, but the password is incorrect, then even anonymous access will fail.

pellelon · Answer

Thanks, I will look into Windows user credentials.&nbsp;And yes, we have tried both hostname and IP address to try to login.I just heard from the user (julia) that she has a&nbsp; "Windows 11 laptop with face recognition, if that fails I use a 6-digit code".The passwd on the Nas is NOT a 6-digit code.&nbsp;But, again, surely you must be able to still logon to the Nas with "different credentials"?&nbsp;I tried that myself on my Nas (same hw). Julia still has an account on that, with a password I didn´t remember, so I changed it and after that I could mount her Home folder share in my Windows 10 box without problems. Note that I had to unmount my own shares first, because a Windows (or ReadyNas?) message popped and said that there can only be one user at a time that mounts shares&nbsp;&nbsp;&nbsp;

StephenB · Answer

pellelon&nbsp;wrote:
&nbsp;
I just heard from the user (julia) that she has a&nbsp; "Windows 11 laptop with face recognition, if that fails I use a 6-digit code".
The passwd on the Nas is NOT a 6-digit code.
&nbsp;

The 6-digit code is a PIN, and it is not the same as her Windows password.&nbsp; Though it is possible that if she normally uses face recognition and the PIN that she no longer knows what the Windows password is.
&nbsp;
pellelon&nbsp;wrote:
Note that I had to unmount my own shares first, because a Windows (or ReadyNas?) message popped and said that there can only be one user at a time that mounts shares
&nbsp;

Windows.&nbsp; As I said before, it only allows one user/password at at time for network shares/SMB.&nbsp; Hence the need for net use * /del /y
&nbsp;
pellelon&nbsp;wrote:
&nbsp;
I tried that myself on my Nas (same hw). Julia still has an account on that, with a password I didn´t remember, so I changed it and after that I could mount her Home folder share in my Windows 10 box without problems.
&nbsp;

So the next (likely final) step is to put a credential in the credentials manager that includes the correct hostname and also the right password.&nbsp; Alternatively, leave the password out (leaving just the user name) - then Windows should prompt her for the password.

Forum Discussion

ReadyNAS 102 user login failure to Home folder

6 Replies

Related Content

ReadyNAS backup definition failure

Confusing ReadyNAS Folder Navigation

ReadyNas RNR4000 Power supply failure

D6220 upgrade failure

ReadyNAS 102 - Sharing Folders

NETGEAR Academy

ProSupport for Business