UK’s trusted IT infrastructure partner since 2003
Servnet
ConfiguratorGet in Touch
Shared/network drive not showing: how to fix it — networkShared/network drive not showing: how to fix it — reach
Troubleshooting

Shared/network drive not showing: how to fix it

Marcus Whitfield · Infrastructure Consultant8 min read

When the shared drive vanishes, a whole team can be stopped at once - the files everyone works from are suddenly unreachable. It is alarming, but it is rarely lost data; far more often it is a connection or permission hiccup between the computer and the place the files live. This guide walks through the fixes in order, from the one-person glitch to the whole-office outage.

A shared drive is a central folder
connectYour PCmaps S: driveColleague PCmaps S: driveNetworkthe pathServer / NASfiles live here

First: is it just you, or everyone?

This single question decides everything that follows, so ask it first. If the shared drive has disappeared for one person while colleagues can still reach it, the problem is on that one computer. If it has vanished for everyone, the problem is at the source - the server or NAS where the files actually live - or the network connecting to it.

A network or shared drive is simply a folder that lives somewhere central - a server, or a NAS box - which your computer connects to and displays as if it were a local drive (often a mapped letter like S: or a shortcut). When it 'disappears', that connection has dropped. Knowing whether it dropped for one machine or all of them tells you exactly where to look.

If it is just your computer

When colleagues are fine and only you are cut off, work through the single-machine fixes. These resolve the large majority of one-person cases.

  • Restart your computer. A mapped drive often fails to reconnect after sleep or a network blip, and a reboot re-establishes it cleanly.
  • Check you are on the right network. If you are on guest Wi-Fi, a phone hotspot, or off the VPN when working remotely, you will not reach internal drives - reconnect to the proper network.
  • Reconnect or re-map the drive. The saved mapping can break, especially after a password change; removing and re-adding it with current details usually fixes it.
  • Confirm your sign-in still works. A network drive checks who you are, so an expired or changed password can quietly lock you out of it.

If it has disappeared for everyone

When the whole office loses the drive at once, stop trying to fix individual computers - the fault is central, and the most likely answers are few. Either the server or NAS hosting the files has a problem (it may have crashed, run out of space, or simply need restarting), or the network path to it is down.

This is not usually a job to improvise on the live server, because the wrong move on a storage box can turn an outage into something worse. The right first steps are to check whether the server or NAS is powered on and responding, and whether other central services are also affected (which would point at the network rather than the storage). If the device hosting everyone's files is unwell, that is firmly a call-for-help moment - and a reminder of why what is on that drive needs protecting, which we come back to below.

Network drive recovery checklist
Shared drive not showing — control mapWHOIs it just you or everyone affected?CORENETOn the right network, not guest or off-VPNCOREMAPRestart, then reconnect or re-map the driveCOREAUTHSign-in still valid after any password changeCORESRVServer or NAS powered on and respondingPLUSPERM"Access denied" handled as a permissions changePLUSBCKDrive backed up under the 3-2-1 ruleOPT

The permissions trap

A subtler version catches people out: you can see the drive, but cannot open it, or can open it but not save - 'access denied'. The connection is fine; what has changed is permission. Network drives deliberately control who can reach what, so the right people see the right folders and no one else.

This commonly happens after staff changes, a reorganised folder structure, or someone being moved between teams or groups. It is not a fault to brute-force around - quietly widening access to fix one person is how sensitive files end up exposed to the whole company. Who can reach which folder is exactly the kind of control that belongs under proper identity and access management, and getting it changed correctly is safer than improvising.

The bigger lesson: protect what is on it

A drive that merely will not show is, with luck, a connection nuisance you reconnect and forget. But the scare is a useful prompt, because the same files becoming genuinely unreachable - through hardware failure, accidental deletion or ransomware - is a far worse day, and one many businesses are quietly unprepared for.

Two principles matter. First, the shared drive must be backed up properly, following the 3-2-1 backup rule so a failure or an attack does not take the only copy with it. Second, do not assume the storage box's own redundancy is a backup - it is not, as we explain in our wider guidance. Making sure the data behind that drive is genuinely safe is core to infrastructure and resilience work, and it is far cheaper to arrange before the bad day than after it. If you are weighing where shared files should live, our guide to a NAS for small business is a sensible next read.

Key takeaways
  • Ask one question first: has the drive vanished for just you, or for everyone? It decides where the fault is.
  • For one person, a restart, the right network and re-mapping the drive fix most cases.
  • If it is gone for the whole office, the server or NAS - or the network to it - is the problem, and that is a call-for-help moment.
  • Seeing the drive but getting 'access denied' is a permissions issue, not a connection one - fix it properly, not by widening access.
  • Treat the scare as a prompt: make sure the shared drive is genuinely backed up under the 3-2-1 rule.
Frequently asked

FAQs — Shared/network drive not showing

Getting it back

The shared drive disappeared for me but works for colleagues - what do I do?

The problem is your computer, not the drive. Restart it, make sure you are on the proper office network (not guest Wi-Fi or off the VPN), and reconnect or re-map the drive with your current sign-in details. A recent password change is a common cause, so confirm your login still works.

I can see the drive but get "access denied" when I open it - why?

That is a permissions problem, not a connection one. Network drives control who can reach which folders, and your access may have changed after a staff move or a folder reorganisation. It should be corrected properly through whoever manages permissions, rather than by widening access, which can expose sensitive files.

When it is serious

The drive has vanished for the whole office - is our data lost?

Almost certainly not lost - usually the server or NAS hosting the files needs attention, or the network to it is down. The files are typically still there once the device or connection is restored. Avoid improvising on the storage box itself, as a wrong move can make things worse; this is a get-help moment.

Is the shared drive automatically backed up?

Not unless someone has set that up - and a storage box's built-in redundancy is not a backup. If the only copy of your files lives on that drive, a failure, deletion or ransomware attack can take it for good. Follow the 3-2-1 backup rule so there is always an independent, protected copy.

Related

Got a question this article didn't answer?

One conversation with an engineer who's done this before. No sales script.

Talk to Servnet →