Windows
Mapped network drive would not resolve or stay connected
The user could not access the P: mapped drive to save files. The drive was remapped using the server IP address instead of name resolution, and both drive letters mapped successfully afterward.
Killed once by someone from XL.net, on 2026-10-30.
Affects
Versions
- Windows
What you see
- P: drive could not be opened for saving files
- Mapped drives would not resolve when connecting
- Drive letters did not map until the path was changed to an IP address
Why it happens
Likely Suspected DNS or name-resolution failure prevented the mapped drives from resolving
When it shows up
A Windows computer can reach the file server by IP but mapped drives fail to resolve by name
You are in this case if:
- Mapped drive letter fails while direct IP access works
- Windows mapping connects only after using the server IP address
- Cached credentials are saved locally after the remap
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-10-30. It is written up from that one repair, so it cites no outside page.