macOS Doesn't Remember a Network Folder Account

macOS fails to remember network folder credentials because the system keychain often conflicts with legacy authentication protocols or corrupted login items. To resolve this, you must remove the existing cached entries from Keychain Access and re-establish the connection using "Remember this password in my keychain." This process ensures that modern macOS versions properly store the authentication tokens required for persistent access to SMB or AFP shares.

Understanding the Authentication Failure

When you connect to a network folder via Finder using Command+K, macOS attempts to authenticate against the server. In many cases, especially with older servers or specific Samba configurations, the operating system does not prompt you to save the credentials. Even if it does, the next time you attempt to mount the share, the system may present a blank dialog or immediately disconnect without asking for input again. This behavior is rarely a bug in the traditional sense but rather a security feature or a caching error within the Keychain Access utility. macOS stores network passwords in the Login keychain by default. If an entry exists but is malformed, expired, or associated with a slightly different server path (such as 192.168.1.50 versus smb://nas.local), the system cannot match the new request to the stored credential. Consequently, it treats the connection as unauthenticated. For users who frequently switch between different network environments or manage multiple storage devices, this issue can become frustrating. It disrupts workflows that rely on automatic mounting of shared drives at login. While some users might try to adjust network settings in System Preferences, the root cause almost always lies in the integrity of the stored keychain items. Addressing the cache directly is the most reliable method to restore functionality.

Clearing Corrupted Keychain Entries

The first step in troubleshooting is to ensure that no stale or conflicting credentials are blocking the new authentication attempt. You need to manually inspect the Keychain Access application to identify any lingering records related to the network share. Open Keychain Access from your Applications/Utilities folder. In the left sidebar, select Login under the Keychains section. Then, use the search bar in the top right corner to type the IP address or hostname of your network folder. For example, if your server is at 10.0.0.5, search for that exact string. You will likely see several results. Look for items named Internet Password. These entries contain the username and encrypted password used to access the share. Select all relevant entries and press the Delete key, or right-click and choose Delete. Confirm the deletion when prompted. This action clears the slate, forcing macOS to treat the next connection attempt as a fresh login. It is important to note that simply deleting the entry does not disconnect the current session if one is active. You should also eject the network drive from the Finder sidebar before proceeding to ensure a clean state. This step is crucial because macOS might continue to use the cached memory of the previous connection even after the keychain entry is removed.

Re-establishing the Connection Correctly

Once the old credentials are purged, you must reconnect to the network folder with the correct options selected. Open Finder and press Command+K to open the Connect to Server dialog. Enter the full server address, such as smb://username@server-ip/share or just smb://server-ip/share. Click Connect. A dialog box will appear requesting your username and password. Here is the critical part: ensure that the checkbox labeled Remember this password in my keychain is checked. If this box is unchecked, macOS will ask for the password every single time you access the folder. By checking it, you allow the system to write a new, valid entry to the Login keychain. After entering your credentials, click Connect. The folder should now mount successfully. To verify that the fix worked, restart your Mac. Upon reboot, check if the network folder appears automatically in the Finder sidebar or mounts silently in the background. If it does, the issue is resolved. If it still fails, there may be deeper network configuration issues, such as port restrictions. For more advanced connectivity problems involving non-standard ports, you might find additional insights in our guide on Connecting to Samba Shares from Mac OS with Different Port.

Advanced Troubleshooting Steps

If clearing the keychain and reconnecting does not solve the problem, consider checking for broader system glitches. Sometimes, the keychaind process, which manages keychain operations, becomes unresponsive. You can force a restart of this service by opening Terminal and running killall keychaind. This command terminates the daemon, causing macOS to restart it automatically, which can refresh the credential handling pipeline. Another potential culprit is the networkd configuration. If your Mac obtains its IP address via DHCP, changes in the network environment can sometimes invalidate cached DNS resolutions for network shares. Restarting the network services by toggling Wi-Fi off and on, or restarting the router, can help establish a fresh handshake with the server. Additionally, ensure that your Mac and the network server are using compatible encryption standards. Older servers might require disabling TLS 1.3 in certain macOS versions due to compatibility bugs. While rare, checking the server's documentation for supported protocols can provide clues if standard fixes fail.

Frequently Asked Questions

Why does macOS forget my network password only sometimes?

This usually happens when the server path changes slightly, such as switching from an IP address to a Bonjour name like .local. Since macOS treats these as different entities, the cached password for one path does not apply to the other, triggering a new authentication prompt that may fail to save.

Can I manually edit the keychain file instead of deleting entries?

No, you should never manually edit the login.keychain-db file directly as it is binary and encrypted. Doing so can corrupt your entire keychain, locking you out of other saved passwords. Always use the Keychain Access GUI to add, view, or delete credentials safely.

Does this issue affect external hard drives connected via USB?

No, this specific issue applies only to network-mounted volumes accessed over Ethernet or Wi-Fi. External drives connected via USB, Thunderbolt, or FireWire do not rely on the same keychain-based authentication protocol for basic mounting, although they may use FileVault or separate disk encryption.

What should I do if the "Remember this password" checkbox is grayed out?

If the checkbox is disabled, it often indicates a permissions issue with the Login keychain or a conflict with third-party security software. Try unlocking the keychain in Keychain Access by entering your Mac user password, then attempt the connection again. If the issue persists, create a new keychain item manually in Keychain Access with the type set to Internet Password.

How can I automate the mounting of network folders at startup?

You can use the Login Items section in System Settings under General. However, a more robust method is to use a launchd plist file or a script that runs mount_smbfs or mount_cifs commands. This ensures the drive mounts reliably before user applications start, avoiding race conditions where apps try to access the drive before it is ready.