---
title: "The share does not exist on the server in Finder on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/finder-share-does-not-exist-on-the-server"
description: "Finder says The share does not exist on the server. Check the share name, the case and the path in Connect to Server."
---

# “The share does not exist on the server” in Finder on Mac

The Mac reached the server, but the share name in the address is not there. The name can have a typing error or the share can be gone.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: “The share does not exist on the server” in Finder on Mac. Read https://kilobat.app/guides/finder-share-does-not-exist-on-the-server.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: macOS 13 Ventura and later. The text was checked in NetAuthAgent on macOS 27.2. · Checked: 10 November 2026

## Symptoms

- Go › Connect to Server fails with “The share does not exist on the server. Please check the share name, and then try again.”
- The server itself answers.
- Other shares on the server open.

## Likely causes

- **A typing error in the share name.** A wrong letter, space or path.
- **The share was renamed or removed.** The administrator changed the server.
- **A share that you may not see.** The account has no rights to the share.

## How to check

1. Test that the server answers on the file sharing port. SMB uses port 445.

   ```
   nc -vz -G 5 server.local 445
   ```
2. Try the address instead of the name. Use Go › Connect to Server and type `smb://192.168.1.10`.
3. Check that your Mac is on the same network as the server. Look at the Network settings.

## How to fix it

1. Open the server by name only, for example `smb://server.local`. Pick the share from the list.
2. Ask the administrator for the exact share name.
3. Check the rights of your account on the share.
4. Delete old shortcuts and favourite servers that use the old name.

## With Kilobat

1. List the network shares that are mounted now, with the server of each. Add `--json` for each share name.

   ```
   kilobat shares
   ```
2. Compare a share that works with the address that fails. Kilobat never opens a share.

## Questions

**Does the case of the name matter?**

It can. Use the name that the server lists.

**Is the network fine?**

Yes. The server answered.

## Sources

- Error text in NetAuthAgent.app, macOS 27.2 (Localizable.loctable)
- [Apple Support: If your Mac can’t connect to another computer](https://support.apple.com/guide/mac-help/if-your-mac-cant-connect-to-another-computer-mchlp1656/mac)
- nc(1), man page installed with macOS 27.2

Checked on 10 November 2026.

## Related guides

- [The Mac cannot connect to a NAS or SMB share](https://kilobat.app/guides/smb-nas-not-connecting-mac): Finder connects to SMB shares with an address such as smb://192.168.1.20/share.
- [Screen Sharing cannot connect to another Mac](https://kilobat.app/guides/screen-sharing-not-connecting-mac): The other Mac must have Screen Sharing on and allow your user.
- [Find the devices on your local network from a Mac](https://kilobat.app/guides/find-devices-on-network): macOS has two built-in ways to see other devices: the ARP table and Bonjour.
- [An app cannot find devices on the local network](https://kilobat.app/guides/local-network-permission): macOS 15 Sequoia and later ask before an app connects to devices on your local network.
