Back to Blog
    MacBook showing a no-network icon on macOS Catalina wallpaper, beside a NAS drive, with server rack in background

    Why Does My Mac Keep Losing Its Network Drive Connection?

    mac
    network drive
    smb
    nas
    networking
    troubleshooting
    Author: Fix My PC Store Editorial TeamPublished: 10/14/2026Last Updated: 10/14/2026

    TL;DR: Mac network drive disconnections are almost always caused by one of three things: the Mac sleeping and not reconnecting cleanly, macOS defaulting to a finicky SMB version, or the router handing out a different IP to the drive's host. Work through the checklist below in order and you'll likely fix it without touching a single preference pane twice.

    What You Need

    • Admin access on your Mac
    • The IP address or hostname of the file server or NAS
    • Access to your router's admin page (usually 192.168.1.1 or 192.168.0.1)
    • About 20 minutes

    No special software required for most fixes. A few steps use Terminal, nothing scary.

    Step 1: Stop the Mac from Killing the Connection When It Sleeps

    macOS aggressively cuts network activity during sleep to save power. When the Mac wakes, it does not always re-mount network volumes cleanly. (Apple calls this a feature. Repair folks call it a headache.)

    Fix it:

    1. Open System Settings (or System Preferences on older macOS).
    2. Go to Battery (or Energy Saver on older Macs).
    3. Turn on Prevent automatic sleeping when the display is off if the machine is a desktop or plugged-in laptop.
    4. On laptops, look for Wake for network access and enable it.

    If you still need the Mac to sleep, use a login item to remount the drive on wake. More on that in Step 5.

    MacBook on desk showing Finder window with disconnected network drive icon, beside a 4-bay NAS device and blue Ethernet cable.
    A dropped network drive connection is one of the most common Mac frustrations , and usually fixable in minutes.

    Step 2: Check Whether the Server's IP Address Is Changing

    If the file server or NAS gets a new IP from the router every so often, your Mac's saved mount point becomes invalid. This is the single most common cause of intermittent disconnections.

    How to tell:

    • Note the IP address shown in Finder's Connect to Server dialog (Cmd+K).
    • Check it again after the next disconnection.
    • If the number changed, you have a DHCP problem.

    Fix it:

    Log into your router and assign a static (reserved) DHCP lease to the NAS or server using its MAC address. The router keeps giving the device the same IP, permanently. Every decent consumer router supports this. If yours does not, consider replacing it.

    Alternatively, connect to the server by hostname instead of IP address if your network has a working DNS or mDNS setup. Macs handle hostnames more gracefully than raw IPs.

    Step 3: Force macOS to Use a Stable SMB Version

    macOS and Windows SMB implementations have argued with each other for years. (It is not a fair fight and nobody wins.) By default, macOS negotiates the SMB version dynamically, and sometimes lands on one that drops idle connections.

    Fix it via Terminal:

    Create or edit the nsmb.conf file to restrict negotiation to SMB 2 and SMB 3 using the documented protocol_vers_map bitmask. A value of 6 enables SMB 2 and SMB 3 while disabling SMB 1:

    sudo nano /etc/nsmb.conf
    

    Add these lines:

    [default]
    protocol_vers_map=6
    notify_off=yes
    

    Save (Ctrl+O, Enter, Ctrl+X) and reboot. The protocol_vers_map=6 directive is Apple's documented bitmask approach for controlling SMB version negotiation (bits: SMB1=1, SMB2=2, SMB3=4; value 6 = SMB2+SMB3). The notify_off=yes line stops the Mac from pestering the server with change-notification packets that some NAS devices handle poorly.

    If you are connecting to a Mac file server instead of Windows or a NAS, skip this step. AFP or SMB3 with default settings usually works fine between two Macs.

    Computer acting up? Get a real diagnosis. Book a free diagnostic

    Step 4: Adjust Server Connection Timeout Settings

    Some NAS devices and Windows file servers close idle connections after a few minutes. macOS does not always reconnect automatically when you try to access the drive again.

    On a Windows server, an admin can run:

    net config server /autodisconnect:-1
    

    That disables the idle disconnect. Use it carefully in environments with many concurrent users.

    On a NAS, check the admin panel for an SMB idle timeout or "session keep-alive" setting. Synology and QNAP both have this option buried in their SMB service settings.

    Step 5: Remount the Drive Automatically at Login or Wake

    Even if you fix the root cause, adding an automatic remount is cheap insurance.

    Option A: Login Items

    1. Mount the drive manually once.
    2. Open System Settings > General > Login Items.
    3. Add the mounted volume. macOS will attempt to reconnect it at every login.

    Option B: A Small Script

    For wake-from-sleep remounting, a basic shell script triggered by a launch agent is more reliable. This gets into intermediate Mac admin territory. If you are not comfortable with launchd, this is a reasonable point to hand it off.

    Step 6: Rule Out Wi-Fi as the Culprit

    If the Mac connects to the file server over Wi-Fi, the drive will drop every time the wireless connection hiccups. This is obvious in hindsight and easy to miss.

    Quick test: Connect via Ethernet and see if the disconnections stop. If they do, the problem is the Wi-Fi, not the SMB configuration or the server. Common causes include a weak signal, a congested 2.4 GHz channel, or a router that aggressively parks inactive Wi-Fi clients.

    For a business environment, intermittent Wi-Fi that costs people file access is a networking problem worth solving properly. See business networking support for what a managed approach looks like.

    Common Mistakes

    Skipping the static IP fix and jumping straight to scripting. If the server's address keeps changing, no mount script will save you. Fix DHCP first.

    Using SMB 1 as a "compatibility" fallback. SMB1 is deprecated, has known security vulnerabilities, and is disabled by default on modern Windows and macOS for good reason. Do not re-enable it. If something requires SMB1, that thing needs to be updated.

    Blaming the Mac when the NAS firmware is stale. NAS manufacturers push firmware updates that fix SMB compatibility bugs. Check for updates on the NAS admin panel before spending two hours in Terminal.

    Saving the server by IP without reserving that IP. Bookmarking smb://192.168.1.50 works great until the router gives that address to a different device.

    Bottom Line

    Ninety percent of Mac network drive disconnections come down to sleep settings, a changing server IP, or SMB version negotiation going sideways. Work through Steps 1 through 3 first. If the problem is in a business environment with multiple users affected, or if the Wi-Fi diagnosis points to a broader network issue, that is worth getting looked at by someone who can see the whole setup.

    For business IT and networking help in the West Palm Beach area, Fix My PC Store can take a look. For Mac-specific hardware or software problems that go beyond network config, Mac repair services are available at the Okeechobee Boulevard shop. Initial checks are free for most standard in-store issues.


    Computer acting up? Get a real diagnosis.

    Fix My PC Store has repaired thousands of machines across West Palm Beach. Free diagnostics, honest pricing, no upsell games.

    Book a free diagnostic

    Frequently Asked Questions

    Does this problem happen more often after a macOS update?
    Yes, occasionally. Major macOS updates sometimes reset SMB negotiation settings or change how the system handles wake-from-sleep network reconnection. If disconnections started right after an update, revisit the nsmb.conf settings in Step 3 and check whether your NAS firmware has a compatibility update for the new macOS version.
    Will using AFP instead of SMB fix the disconnection problem?
    AFP (Apple Filing Protocol) was deprecated by Apple and is no longer supported in macOS Ventura and later. Even on older macOS versions, AFP can be less stable than a properly configured SMB3 connection. Switching to AFP is not a recommended fix.
    My Mac is on a work domain and I cannot change router settings. What can I do?
    Talk to your IT administrator about assigning a static DHCP reservation for the file server. You can still apply the nsmb.conf tweak in Step 3 yourself, since that only changes your Mac's client behavior. If the problem is company-wide, the IT team needs to look at the server's idle timeout settings.
    Can a VPN cause Mac network drive disconnections?
    Yes. If the drive is hosted on a remote network accessed via VPN, any VPN interruption will drop the drive. Also, some VPN clients on Mac interfere with local network discovery even for on-premises shares. Try disconnecting the VPN and testing local drive stability separately.

    Share this article