Mapped Network Drive Shows a Red X or Keeps Disconnecting? It's by Design — Here's the Real Fix

A mapped network drive shows a red X (or “Disconnected”) in File Explorer — yet the moment you click it, it opens fine. Or it drops after about 15 minutes of not using it.

This is expected behavior, not a fault. Windows’ Server service auto-disconnects idle SMB sessions after 15 minutes to free resources, so Explorer paints a red X on the now-idle mapping. The connection re-establishes instantly the moment you access it. So before you replace cables or blame the NAS:

Why the common “fixes” don’t stick: forums tell you to disable “reconnect at sign-in,” edit the client, or buy a new switch. None of that changes the 15-minute idle timeout, which lives on the host (the machine sharing the folder). That’s the only setting that actually controls this.

Fix 1: Decide whether you even need to “fix” it

If the drive works the instant you click it, nothing is broken — the red X is cosmetic. Many people simply ignore it. If the red X causes a real problem (a backup job or app that checks the drive without opening it fails), change the timeout below.

Fix 2: Raise (or disable) the idle timeout on the host

Run this on the computer or server that shares the folder, in an admin Command Prompt:

net config server /autodisconnect:-1

• -1 disables the idle auto-disconnect.
• Or set minutes, e.g. /autodisconnect:240 for 4 hours.

The equivalent registry value (host side): HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\autodisconnect (REG_DWORD, minutes). Restart the Server service or reboot to apply.

Fix 3: Keep the session alive from the client (when you don’t control the host)

If you can’t change the NAS/host (e.g., it’s a corporate server), you can stop the client from idling out:

• A scheduled task that touches the share periodically keeps the session active, or
• Map with net use \\server\share /persistent:yes and let it reconnect on access (the red X stays, but access is seamless).

Fix 4: Rule out a real drop

If the drive won’t reconnect on click (not just a red X), it’s a genuine connection issue, not autodisconnect — check name resolution (try the IP), that the host is online, and credentials in Credential Manager. A different error like 0x80070035 points to SMB/sharing problems, not idle timeout.

FAQ

Why 15 minutes specifically? That’s the Windows default for autodisconnect on the Server service. It’s a resource-management feature, not a bug.

Do I change this on my PC or the server? The host that shares the folder — the timeout is enforced server-side. Changing it on the client does nothing.

Will disabling autodisconnect hurt performance? On a small office/home network, negligibly. On a busy server with many clients, prefer a longer timeout (e.g., 240) over -1.

Sources: Microsoft Learn — Mapped drive connection to network share is lost