How to Map a NAS Network Drive on Windows, Mac & Linux
12 min read
2,203 words
If you own a NAS, mapping a network drive is the single most important step to making that storage feel like a local hard drive on your computer. This guide walks you through the exact process on Windows, macOS, and Linux, covering both the quick graphical method and the more reliable permanent mount that survives a reboot. We also cover the most common reasons a NAS share stops showing up and how to fix them. This guide breaks down network drive mapping guide in practical terms.
By the end of this guide, you will be able to access your NAS share as a drive letter (Windows), a mounted volume (Mac), or a persistent mount point (Linux) — and you will know exactly what to check when it breaks.
How to Map a NAS Drive on Windows 10 and 11
Mapping a NAS drive on Windows is done through File Explorer. The process is identical on Windows 10 and 11, and the mapped drive can be set to reconnect automatically every time you log in.
If your NAS supports SMB 3.0 (most modern units do), enable SMB 3.0 encryption on the NAS side for a faster and more secure connection. This is a setting in your NAS operating system, not in Windows.
Step 1: Open File Explorer and Map the Drive
Press Win + E or click the folder icon in the taskbar.
In the left sidebar, right-click “This PC” and select “Map network drive…” from the context menu.
Pick any available letter (Z: is common). You can also leave it as the default next available letter.
Type the path to your NAS share in the format \\NAS-NAME\Share-Name or \\192.168.1.100\Share-Name. Replace with your NAS’s actual IP or hostname and share name.
Check “Reconnect at sign-in” to make the drive persist after a reboot. If your NAS requires different credentials than your Windows login, check “Connect using different credentials” and enter your NAS username and password.
Windows will attempt to connect. If successful, the new drive appears under “This PC” with the letter you chose.
Step 2: Verify the Mapped Drive Appears After Reboot
After mapping, restart your computer and check that the Z: drive (or whatever letter you chose) appears in File Explorer without needing to re-map it. If it does not appear, the most common causes are: the NAS was not fully booted before Windows tried to connect, or the NAS credentials are not being saved correctly. See the troubleshooting section below.
How to Mount a NAS Share on macOS
macOS connects to NAS shares using the SMB protocol (Windows File Sharing) or AFP (Apple Filing Protocol, older). The process is done through Finder, and for a permanent mount, you add the share to your Login Items.
Step 1: Connect via Finder
Click the Finder icon in the Dock.
From the top menu bar, click Go > Connect to Server, or press Cmd + K.
Type smb://192.168.1.100/ShareName (replace with your NAS IP and share name). For older NAS units that still use AFP, you can use afp://192.168.1.100/ShareName instead.
macOS will attempt to connect. If the NAS requires authentication, a login window appears — enter the NAS username and password.
If the NAS has multiple shares, you will be prompted to select which one to mount. Choose the share and click OK.
The share now appears on your desktop and in the Finder sidebar under “Locations.”
Step 2: Make the Mount Permanent (Login Items)
To have the NAS share mount automatically every time you log in, you need to add it to your Login Items. However, a simple shortcut in Login Items does not work reliably — you must use a script or an app that reconnects the share.
The most reliable method is to use the free app AutoMounter or create a simple AppleScript that runs at login. A common approach is to open System Settings > General > Login Items & Extensions, then add a script that runs mount_smbfs or a saved Finder connection. If the share disconnects after sleep, the NAS may be going to sleep or the Mac’s network stack may be resetting. Setting the NAS to never sleep and disabling “Put hard disks to sleep when possible” on the NAS can help.
macOS Ventura and later have stricter security around Login Items. If your mapped share keeps disappearing, check that your NAS is using SMB 2 or 3 (not SMB 1, which is disabled by default on modern macOS). Many older NAS units default to SMB 1 — you must enable SMB 2/3 in the NAS control panel.
How to Mount a NAS Share on Linux
Linux offers two main ways to mount a NAS share: using the file manager GUI (which is temporary) or adding a persistent entry to /etc/fstab (which survives reboots). The latter is the recommended approach for a homelab.
Option 1: Mount via GUI (Temporary)
Most Linux desktop environments (GNOME, KDE, Cinnamon) can browse and mount SMB shares through the file manager. In Nautilus (GNOME), click “Other Locations” in the sidebar, then enter smb://192.168.1.100/ShareName in the “Connect to Server” box at the bottom. Enter credentials when prompted. The share appears in the sidebar under “Network” but unmounts when you log out or reboot.
Option 2: Mount via /etc/fstab (Persistent)
This is the most reliable method for a homelab server or a workstation that needs constant access to NAS storage.
Open a terminal and run sudo apt install cifs-utils (Debian/Ubuntu) or sudo dnf install cifs-utils (Fedora/RHEL). This package provides the tools needed to mount SMB shares.
Run sudo mkdir /mnt/nas to create a folder where the share will be mounted. You can name it anything you like.
To avoid storing your NAS password in plain text in fstab, create a file: sudo nano /etc/smbcredentials. Add two lines: username=your_nas_username and password=your_nas_password. Save the file, then run sudo chmod 600 /etc/smbcredentials to restrict permissions.
Run sudo nano /etc/fstab and add this line at the bottom (adjust the IP, share name, and mount point):
//192.168.1.100/ShareName /mnt/nas cifs credentials=/etc/smbcredentials,iocharset=utf8,uid=1000,gid=1000,file_mode=0755,dir_mode=0755 0 0
Replace uid=1000 and gid=1000 with your user’s UID and GID (run id in the terminal to find them).
Run sudo mount -a to mount all entries in fstab. If there are no errors, the share is now mounted at /mnt/nas. Reboot to confirm it mounts automatically on boot.
If the NAS is not reachable at boot (e.g., it boots more slowly than your Linux machine), the fstab mount will fail and may delay the boot process. To prevent this, add the nofail option to the fstab line: //192.168.1.100/ShareName /mnt/nas cifs credentials=/etc/smbcredentials,nofail,iocharset=utf8,uid=1000,gid=1000,file_mode=0755,dir_mode=0755 0 0. This tells the system to continue booting even if the mount fails.
Why a NAS Share Suddenly Disappears (And How to Fix It)
A NAS share that worked yesterday but is gone today is a very common frustration. Here are the most likely causes, in order of frequency.
1. The NAS IP Address Changed
If your NAS uses DHCP (automatic IP assignment) and your router reboots, the NAS may receive a different IP. Your computer is still trying to connect to the old IP. The fix is to assign a static IP to your NAS via your router’s DHCP reservation feature, or set a static IP directly on the NAS itself. After changing the IP, you must remap the drive on all connected computers using the new IP.
2. The NAS Went to Sleep
Many consumer NAS units have a power-saving feature that spins down hard drives or puts the entire unit to sleep after a period of inactivity. When you try to access the share, the NAS may take 30-60 seconds to wake up, and some operating systems (especially Windows) give up before the NAS responds. The fix is to disable disk spindown and NAS sleep settings in the NAS control panel, or accept the delay and configure your OS to retry the connection.
3. Windows Credential Manager Has Stale Credentials
If you changed your NAS password, Windows may still be using the old credentials stored in Credential Manager. Open Control Panel > Credential Manager > Windows Credentials, find the entry for your NAS (it will look like TERMSRV/192.168.1.100 or MicrosoftAccount/...), and remove it. Then remap the drive with the correct password.
4. SMB Protocol Version Mismatch
Modern Windows, macOS, and Linux distributions disable SMB 1.0 for security reasons. If your NAS is old and only supports SMB 1.0, you will not be able to connect. Check your NAS settings for an option to enable SMB 2 or 3. If the NAS truly cannot support SMB 2+, consider replacing it or using a different protocol like NFS (Network File System).
If you are running a custom NAS OS like TrueNAS or Unraid, check the SMB service settings. TrueNAS Scale, for example, defaults to SMB 3.0. Unraid defaults to SMB 2/3. Both are compatible with modern clients. If you are using an older version of either, update to the latest stable release.
Bottom Line: Which Mounting Method Should You Use?
For a home user who just wants to access files, the graphical methods (Windows File Explorer, Mac Finder, Linux file manager) are perfectly adequate for temporary access. For a homelab environment where the NAS is used for Docker containers, media servers, or automated backups, the persistent mount (Windows “Reconnect at sign-in,” Mac Login Items with a script, Linux /etc/fstab) is non-negotiable.
If you are running a Docker server on Linux (such as the one described in our Best Docker Server Build 2026 guide), mounting your NAS via /etc/fstab is the standard approach — it ensures your containers always have access to network storage without manual intervention.
Regardless of your OS, the most important step is to give your NAS a static IP address. Without that, any persistent mount will eventually break when the IP changes. Once you have that in place, choose the method above for your OS, test it with a reboot, and you are set.
Remember that RAID is not a backup — it protects against drive failure but not against accidental deletion, corruption, or disasters.
Frequently Asked Questions
How do I map a NAS drive permanently on Windows?
To map a NAS drive permanently on Windows, open File Explorer, right-click “This PC,” and select “Map network drive.” Choose a drive letter, enter the NAS path (e.g., \\192.168.1.100\ShareName), and check the box “Reconnect at sign-in.” If your NAS requires different credentials, check “Connect using different credentials” and enter them. The drive will then remount automatically every time you log in, provided the NAS is on the network and reachable at boot.
Why does my NAS drive disconnect after restarting my Mac?
The most common reason a NAS drive disconnects after restarting a Mac is that the share was mounted via Finder’s “Connect to Server” but was not added to Login Items. macOS does not automatically remount network shares after a reboot unless you configure it explicitly. To fix this, use a third-party app like AutoMounter or create an AppleScript that runs at login. Another cause is that the NAS IP address changed — ensure your NAS has a static IP assigned via your router’s DHCP reservation.
How do I mount a NAS share automatically on Linux boot?
To mount a NAS share automatically on Linux boot, you add an entry to /etc/fstab. First, install cifs-utils with your package manager. Create a credentials file for security (e.g., /etc/smbcredentials), then add a line like //192.168.1.100/ShareName /mnt/nas cifs credentials=/etc/smbcredentials,iocharset=utf8,uid=1000,gid=1000,file_mode=0755,dir_mode=0755 0 0 to /etc/fstab. Add the nofail option if the NAS may not be ready when the system boots. Run sudo mount -a to test, then reboot to confirm it works.
Why can’t I see my NAS on the network anymore?
If your NAS has disappeared from the network, start by checking if the NAS itself is powered on and connected to the router (check the NAS’s status LEDs). Log into your router’s admin page and look for the NAS in the DHCP client list — if it is not listed, the NAS may have lost its network connection. If it is listed but has a different IP than before, that is the problem. Assign a static IP to the NAS. Also check that the NAS’s SMB service is enabled and that your computer’s firewall is not blocking SMB traffic (port 445). Finally, verify that your NAS and computer are on the same subnet (e.g., both 192.168.1.x).
Last verified: July 10, 2026. Specifications cross-checked against manufacturer documentation where available.
🛡 Shop Recommended Hardware
Prices and stock verified regularly by our affiliate partners. As an affiliate, HomeLabCost may earn a commission on qualifying purchases at no extra cost to you.
Browse Hardware Picks →
homelabcost
HomeLabCost editor covering NAS builds, hardware selection, and homelab server setup guides.