Unable to access NAS drive when logged in using PIN to AzureAD account

Question

To me this seems like a bug, but I could be wrong. Maybe it's some kind of security feature? I login to Windows 10 (1903) with an AzureAD login. Since that password is pretty long, I prefer to not enter it every time I login and/or after locking my workstation when I leave my desk.

So I'm quite happy that Windows 10 allows me to use a short PIN code to login instead! However when I login with PIN, I am completely unable to access my Synology NAS shared drives. Since the password for my AzureAD login and the password for the Synology drive (with yet another username) are different, I don't understand why the different login would make any difference.

The right credentials are stored in the Credential Manager under Windows Credentials with the IP address of the NAS as Internet or network address.

So if I login with PIN I get a message that the mapped drive R: cannot be mapped, but then if I logout and login again with my AzureAD password, it works flawlessly...

I've found references online from years ago, when Windows 10 was still a Technical Preview, but has this really not been fixed over the course of all these years?!

***Original title: Why am I unable to access my shared drive (Synology NAS) when I log into my Windows account with PIN?***

Answer 1

Hi,

This seems to be a bug and has been reported over and over: When you log in using a password everything works, when using a PIN, the NAS cannot be accessed.

Unfortunately, I was unable to spot this bug for several hours and most of my working day got wasted trying to correct my NAS' configuration... However, I eventually ended up finding the solution more or less by accident (as I could not identify the relation to the PIN login). While Microsoft has still not fixed this (the first bug reports date back to 2015), there is a solution:

Use the Windows search for "Credential Manager" and select "Windows credentials". Remove any preexisting entry for your NAS and add a new windows credential entry using the following structure: 

Server adress: \NameOfYourNAS

Username: NameOfYourNAS\Username

Password: ... 

With this solution you should be able to access the NAS even when logging into Windows with a PIN. However, it may not appear under network drives. If so, simply enter \NameOfYourNAS into the explorer address bar to access it. From there you may also add a shortcut to the navigation.

Credits for this solution go to the user tumas04 on reddit: 

https://www.reddit.com/r/Windows10/comments/3fi7o5/psa_having_a_pin_to_sign_into_windows_will/

Hope this will save others some time and nerves... Cheers!

Answer 2

Hi,

Thank you for writing to Microsoft Community Forums.

I understand that you are facing issues while accessing NAS drive when you use PIN to sign in to your AzureAD account.

Since you are using AzureAD account let me point you in the right direction to get support. I would suggest you to post your query on TechNet forums, where we have expertise and support professionals who are well equipped with the knowledge to assist you with your query.

Regards,

Prakhar Khare

Microsoft Community – Moderator

Answer 3

Thanks Prakhar,

I actually am logging in with a Office365 account, which shows as AzureAD\JorikCaljouw.

But it is interesting you mention AzureAD. I was expecting the PIN vs password issue for network shares to not be exclusive to AzureAD logins. So to double check I created a local user account mounted the same drive (also here my login username/password is not the same as the network drive credentials). Then I added a PIN sign-in and low and behold...

It does work with a local account! Good to know.

I will post my query at TechNet forums now. But it's probably good for others to know (if they find this), that the issue seems to be only with Office365/AzureAD accounts with PIN.

Regards,

Jorik

Answer 4

Thanks Prakhar,

I actually am logging in with a Office365 account, which shows as AzureAD\JorikCaljouw.

But it is interesting you mention AzureAD. I was expecting the PIN vs password issue for network shares to not be exclusive to AzureAD logins. So to double check I created a local user account mounted the same drive (also here my login username/password is not the same as the network drive credentials). Then I added a PIN sign-in and low and behold...

It does work with a local account! Good to know.

I will post my query at TechNet forums now. But it's probably good for others to know (if they find this), that the issue seems to be only with Office365/AzureAD accounts with PIN.

Regards,

Jorik

This was actually meant to be written from the same user as the Topic Starter, but I wasn't careful enough and the link from email opened the page while being signed in with my private Microsoft Account instead of my Business Account. The joys of using multiple Microsoft Accounts (1 for private, 1 for business and 1 for a non-profit organization...)

Answer 5

That's great! I was able to get it to work with this info. I was actually already very close, but since I was always referring to the IP address directly I had entered:

Server address: \192.168.x.y

Username: Username

Password: ...

in the Windows Credential Manager.

And this worked correctly when logging in with PIN or password from a local user. It also worked correctly when logging with password from my AzureAD user, but it would fail with logging in with PIN from my AzureAD user.

Really very frustrating to see such inconsistencies.

Anyway, with your info, the problem is now resolved, I can now login with PIN and my mounted drives just work!