---
title: "There was a problem connecting to the server in Finder on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/finder-problem-connecting-to-the-server"
description: "Finder says There was a problem connecting to the server. Check the name, the network, the port and the server."
---

# “There was a problem connecting to the server” in Finder on Mac

Finder could not open the connection to the file server. The server may be off, on another network, or blocked by a firewall.

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

My Mac has this problem: “There was a problem connecting to the server” in Finder on Mac. Read https://kilobat.app/guides/finder-problem-connecting-to-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: 29 October 2026

## Symptoms

- Go › Connect to Server fails with “There was a problem connecting to the server.”
- Finder can add the name of the server in the message.
- The server shows in Network, but does not open.

## Likely causes

- **The server is off or asleep.** A NAS or a Mac that sleeps does not answer.
- **A wrong name or address.** The name does not resolve, or the address changed.
- **The Mac and the server are on different networks.** Apple says Bonjour and Windows servers must be on the same local network.
- **A firewall on the server.** A Windows server with its firewall on can refuse the connection.

## 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. Start the server and wake it. Check its network link.
2. Use the DNS name or the IP address in place of the display name. Apple gives this advice.
3. Join the same network as the server, or use Go › Connect to Server with the full address.
4. Check the firewall on the server for file sharing.
5. See [The Mac cannot connect to a NAS or SMB share](https://kilobat.app/guides/smb-nas-not-connecting-mac) for SMB settings.

## Questions

**What does the message mean?**

The Mac could not make or keep the connection. It does not say which step failed.

**Why does the name fail and the IP address work?**

The name does not resolve. See [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found).

## 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 29 October 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.
- [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found): When DNS fails, the Mac cannot change a name such as apple.com into an IP address.
