Windows
Cached credentials broke access to mapped drives and Microsoft Access
The user was connected to VPN but could not open Microsoft Access or reach the U: drive. The issue was resolved by removing old cached credential entries and remapping the drives, then confirming Access worked.
Killed once by someone from XL.net, on 2026-04-02.
Affects
Apps
- Microsoft Access
What you see
- VPN is connected, but Microsoft Access will not open the file share content.
- The U: drive is not reachable even though the computer is on VPN.
Why it happens
Likely Corrupted or stale cached credentials on the workstation
When it shows up
A Windows computer is connected to VPN, but a mapped drive or Microsoft Access file-share resource still fails to open.
You are in this case if:
- Windows Credential Manager has old saved entries for the affected share
- The drive/share starts working again after the saved credentials are removed and the drive is remapped
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Someone from XL.net killed this on a Windows computer on 2026-04-02. It is written up from that one repair, so it cites no outside page.