How to fix Mac that cannot connect to or mount a network shared drive (SMB) on macOS
Summary
This guide helps you troubleshoot and resolve: How to fix Mac that cannot connect to or mount a network shared drive (SMB) on macOS. Follow the steps below to fix the issue.
Common Causes
Connecting your Mac to a network shared drive using SMB (Server Message Block) is usually straightforward, but occasionally macOS can refuse to connect or fail to mount the share. This guide walks you through the most common causes and provides step-by-step fixes to get your Mac talking to your Windows server, NAS device, or other SMB share again.
Quick Fix Steps
If you're in a hurry, try these steps in order. Most SMB connection issues are resolved by the first few items on this list.
- Confirm the share is online and reachable from another device on the same network.
- Verify you are using the correct username, password, and share path.
- Restart your Mac and the device hosting the share.
- Connect using
smb://in the Connect to Server dialog. - Sign out of iCloud Drive or disable Optimise Mac Storage if the share is hosted via iCloud.
- Reset your Mac's keychain entry for the share.
- Check for macOS software updates (System Settings > General > Software Update).
Detailed Instructions
1. Confirm the Share Is Reachable
Before changing settings on your Mac, rule out a network or server issue.
- Ping the server from your Mac by opening Terminal (found in Applications > Utilities) and typing
ping -c 4 servername.localorping -c 4 192.168.1.10(replace with your server's address). - Try connecting from another computer or device on the same network.
- Confirm the server, NAS, or PC hosting the share is powered on and not in sleep mode.
2. Connect Using the Correct Protocol and Path
macOS uses different protocols depending on the share type. For Windows shares and most NAS devices, use SMB.
- Open Finder.
- From the menu bar, choose Go > Connect to Server (or press
Command + K). - In the Server Address field, enter the address using the SMB protocol. For example:
smb://nas.local/sharedfoldersmb://192.168.1.50/datasmb://server.example.com/team
- Click Connect.
- When prompted, enter the username and password for the share. If the share allows guest access, choose Guest.
3. Sign In With the Correct Credentials
SMB authentication can be picky about how usernames are formatted.
- For a local account on a Windows PC or NAS, use just the username (for example,
john). - For a Windows domain account, use the format
DOMAIN\usernameorusername@domain.local. - For a Microsoft account, use your full email address.
- Ensure CAPS LOCK is off and that you are not accidentally entering a saved password from another service.
4. Restart Your Mac and the Server
A simple restart clears stale network connections and resets background services that may be blocking the SMB session.
- Save any open work and choose Apple menu > Restart.
- Restart the device hosting the share (NAS, Windows PC, or server).
- Once both devices are back online, try connecting again using Go > Connect to Server.
5. Remove and Re-add the Share From Keychain
macOS stores SMB credentials in Keychain Access. If the password has changed or the saved entry is corrupt, your Mac will keep failing to authenticate.
- Open Applications > Utilities > Keychain Access.
- In the search field, type the server name or IP address (for example,
nas.local). - Select any matching entries and press the Delete key, then confirm.
- Quit Keychain Access and try connecting to the share again. You will be prompted to enter the password fresh.
6. Check macOS Sharing and Firewall Settings
If your Mac is hosting the share, or if a local firewall is blocking outbound SMB traffic, the connection will fail.
- Open System Settings > General > Sharing.
- Ensure File Sharing is turned on if you intend to share folders from this Mac.
- Open System Settings > Network > Firewall and confirm the firewall is not blocking smbd or incoming connections on ports
445and139. - If you use a third-party security app (such as Little Snitch or Lulu), check that SMB traffic to your server's IP address is allowed.
7. Force SMB Signing or Disable If Required
Some older NAS devices and Windows servers do not support modern SMB signing requirements. macOS may refuse to connect if the signing negotiation fails.
- Open Terminal from Applications > Utilities.
- To check the current signing policy, type:
sudo defaults read /etc/nsmb.conf(you may be prompted for your Mac password). - If no file exists, you can create one to relax signing. Type:
sudo nano /etc/nsmb.conf
- Add the following lines:
[default]signing_required=novalidate_neg=no
- Press
Control + Oto save, thenControl + Xto exit. - Restart your Mac and try connecting again.
/etc/nsmb.conf file once you have resolved the issue.8. Mount the Share Automatically at Login
Once the connection works, you can make macOS reconnect to the share every time you log in.
- In Finder, connect to the share using Go > Connect to Server.
- Once mounted, open System Settings > General > Login Items.
- Under Open at Login, click the plus icon and add the mounted share from the list.
- Tick Hide if you do not want a Finder window to open each time.
Troubleshooting
"There was a problem connecting to the server"
This generic error usually indicates the server is unreachable, the share name is wrong, or the SMB service is not running. Verify the server's IP address with ping and confirm port 445 is open by typing nc -zv servername 445 in Terminal.
"You entered an invalid username or password"
The credentials are being rejected by the server. Remove the saved entry from Keychain Access as described in step 5, then re-enter the username in the correct format for your server type.
Share mounts but folders appear empty
This is typically a permissions issue on the server side. Confirm that the user account has read or write access to the share and that any NTFS or filesystem permissions allow access.
Connection works on Wi-Fi but not Ethernet (or vice versa)
macOS may be treating the networks differently. Open System Settings > Network, click the network interface in question, then set Configure IPv6 to Link-local only or Off if your network does not use IPv6.
macOS Sonoma or later prompts for keychain password repeatedly
Apple introduced stricter keychain handling in macOS Sonoma and later versions. If your Mac repeatedly asks for the keychain password when accessing an SMB share, try the following:
- Open Keychain Access (Applications > Utilities > Keychain Access).
- Select the login keychain from the left sidebar.
- From the menu bar, choose Keychain Access > Settings (or Preferences on older versions).
- Ensure Lock after [X] minutes of inactivity is not set too low, or disable Lock when sleeping if you prefer fewer prompts.
- Lock and unlock the login keychain manually by clicking the padlock icon at the top left of the window.
- Try connecting to the share again and allow macOS to save the password permanently when prompted.
Connecting to older NAS or Windows servers that require SMB 1.0
macOS disables SMB 1.0 by default because it is a legacy protocol with known security vulnerabilities. If you are connecting to an older NAS device or Windows server that only supports SMB 1.0, you may see connection failures or authentication errors.
Before enabling SMB 1.0, analyse whether the server can be updated to support SMB 2.0 or later. If you must use SMB 1.0 on a trusted local network:
- Open Terminal from Applications > Utilities.
- Type
sudo nano /etc/nsmb.confand enter your Mac password when prompted. - Add the following lines to the file:
[default]protocol_vers_map=1
- Press
Control + Oto save, thenControl + Xto exit. - Restart your Mac and attempt the connection again.
/etc/nsmb.conf file or change the protocol version once the legacy server is upgraded or replaced.VPN and split-tunnel configurations
If you are connected to a corporate VPN or using a split-tunnel configuration, SMB traffic may be routed through the VPN tunnel or blocked entirely, preventing access to local network shares.
- Disconnect from the VPN and try connecting to the local share again.
- If the share is only accessible via VPN, confirm that split-tunnelling is configured to allow local subnet traffic.
- Check with your IT administrator that port
445is permitted through the VPN tunnel.
Still Need Help?
If you have completed these steps and your Mac still cannot connect to or mount the network share, contact our Australian support team for further assistance.
Still Having Issues?
💻 Open a Ticket