Why Finder shows “operation can’t be completed” on network shares
Short answer: The error means Finder connected to the SMB server (the shared file storage device) but then hit a protocol-level rejection when attempting to read or write files. SMB (Server Message Block) is the file-sharing protocol used by Windows computers and NAS devices. The rejection usually comes from one of three causes: an SMB version mismatch (the NAS is advertising a version macOS does not support fully), packet signing being required by the server but the macOS client is not sending signed packets, or stale Keychain credentials being sent automatically and rejected by the server. All three are software configuration fixes that require no hardware work.
How to fix macOS Finder SMB errors on Indian office networks
Step 1: Clear stale SMB credentials from Keychain
macOS Keychain — the secure credential store — automatically saves SMB login details the first time you connect to a share. If the server password has changed, or if the wrong credentials were saved, Finder silently sends the old ones and gets rejected. Open Keychain Access (search with Spotlight), type the server IP or hostname in the search field, and delete any entries tagged as Network Password for that server. Close Keychain Access and try connecting again from Finder → Go → Connect to Server. This resolves the error in roughly half of cases in a typical Indian office.
Step 2: Force SMB version via nsmb.conf
If credentials are correct but the error persists, the issue is the SMB protocol version negotiation. macOS removed SMB1 client support in Ventura and later — older NAS firmware on devices like QNAP TS-231 or Synology DS218 may not correctly implement SMB2/SMB3. Create or edit the nsmb configuration file:
mkdir -p ~/.config/nsmb
nano ~/.config/nsmb/nsmb.confAdd the following content to force SMB2:
[default]
smb_neg=smb2_only
signing_required=noSave (Ctrl+X, Y, Enter), disconnect from the share in Finder, and reconnect. Setting signing_required=no disables packet signing enforcement on the client side — relevant when the NAS requires unsigned packets but macOS defaults to requesting signed. This combination resolves most Finder SMB errors on Indian NAS hardware from the 2018–2022 era.
Step 3: Update the NAS firmware
The definitive fix for older QNAP and Synology devices is a firmware update. Log into the NAS admin panel (usually the NAS IP in a browser), check for firmware updates, and apply them. Recent QNAP QTS 5.x and Synology DSM 7.x firmware versions have substantially improved macOS SMB3 compatibility. If your IT team manages the NAS, request the firmware update with a reference to the macOS SMB3 compatibility change log.
Step 4: The India angle — mixed OS offices and ageing NAS hardware
Indian SMEs typically run mixed-OS environments — Windows 10/11 machines alongside a few MacBooks used by designers or founders. NAS devices purchased in the 2018–2022 wave are now showing their age with macOS compatibility. Windows clients mask the issue because Windows SMB clients are more permissive with version fallback. The MacBook exposes the underlying protocol gap because macOS enforces stricter SMB compliance. Read our macOS Wi-Fi connection issues guide for related network troubleshooting on Indian office setups.
When to involve a repair or IT service
When the error persists across multiple NAS devices
If the Finder error appears on every network share the MacBook tries to access — different NAS devices, different servers — the issue is in the MacBook's macOS networking stack rather than the server side. A fresh macOS reinstall (non-destructive, preserves data) typically resolves deep SMB stack corruption.
Typical cost
macOS network configuration fixes and SMB troubleshooting: ₹1,000–₹2,000 at a service centre. If a macOS reinstall is needed: ₹1,500–₹2,500. A separate NAS firmware update performed by the IT administrator typically has no additional cost. The ₹149 doorstep visit confirms the root cause — MacBook-side or NAS-side — before any commitment, which saves unnecessary work on the wrong device.
Step 5: Test the connection with the smb:// URL directly
Rather than browsing through Finder's Network section (which relies on mDNS discovery and can fail independently of SMB connection), connect directly using the server address. In Finder, press Command + K, type smb://[server-IP]/[share-name] and click Connect — for example, smb://192.168.1.100/documents. This bypasses the Bonjour discovery layer and tests the pure SMB protocol path. If this direct URL works but browsing via Finder's Network sidebar does not, the issue is in mDNS/Bonjour discovery rather than SMB itself. In Indian offices using older TP-Link or D-Link routers, mDNS multicast packets are sometimes blocked between VLANs — a router configuration issue that the IT administrator needs to resolve separately from the SMB settings.
A note from the LRW Engineer Team
We see this specific error most often when a company buys their first MacBook and tries to connect it to the existing NAS. The IT team sees Windows machines working and assumes the Mac is faulty. It rarely is. The nsmb.conf fix takes under five minutes and usually resolves it on the spot. The Apple MacBook service page covers our network diagnostics process for M-series and Intel MacBook models.