An odd thing happened this morning with one of our users. After logging on to the network she noticed that she did not have access to several shares that she has always had access to. Out of her 7 mapped drives, 5 of them were on the same server and it was 4 of those that were the issue. A usual check of her AD account (password change/expiry, account lockout, etc) revealed no issues there. A reboot didn't solve the problem either. What struck me as strange was that she could only access some of the shares on the one server but not all. I tried removing her permission from an affected share and then readding them back (had her log off and back on again to obtain a new access token) but that didn't work. What I found to work was if I logged her in to a computer that she hadn't used before and tried to access the shares. Everything worked. I thought her local profile might have become corrupted but didn't understand how that would affect accessing network shares. (Also Windows wasn't squawking about it being corrupted but maybe it doesn't need to?) When a domain user logs on, a DC generates a new access token based on a number of things including security permissions right? Is this then stored in a file on the local machine? If so, where? I ended up recreating her local profile directory but all of her configured applications were blown away. Can anyone recommend a different/better way of doing this in case it happens again in the future?

Hi, Please try to access the shared folder via UNC path. If we can access the resources via this method, please remove the existing network mapping. Then create a new network mapping for the share to fix the issue. Best Regards, Kim ZhouPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.