iPhone Files app can't connect to server (smb://): every fix

By Isaac Griffiths, developer of SMBDrop · 15 October 2026

The Files app's Connect to Server is a decent little SMB client when it works. When it doesn't, the error messages don't give you much to go on. This page covers the two families of error you're most likely to see, what's behind them in the reports I've found, and how to fix each one.

The messages people report include:

"There was a problem connecting to the server." Check the server name or IP address, and then try again.
"The operation couldn't be completed." followed by Operation not supported, Permission denied, Invalid argument or RPC struct is bad.
"The operation can't be completed because an unexpected error occurred."

If yours ends in "Socket is not connected", that has its own page. Honestly, I couldn't tie every sub-message to one cause, because most of them come from a single forum thread each. The fixes below are ordered by how often they solved it for people.

Start here: the basics

Apple's own steps are: open Files, tap Browse, tap the More button (⋯), choose Connect to Server, enter a local hostname or network address, and tap Connect. Then choose Registered User and sign in (Guest only works if the server allows it). Check that:

The iPhone is on the same Wi-Fi as the server, not a guest network, and any VPN is off.
You typed smb:// and the server's IP address, like smb://192.168.1.40. If the IP works and the name doesn't, it's a name resolution problem and you can just keep using the IP.
The SMB service is switched on and you've shared at least one folder. The server guides for Synology, Windows and Unraid and TrueNAS cover this.

"Operation not supported": check the SMB versions

A protocol mismatch between the server and the iPhone is one reported cause, so check the server's minimum and maximum SMB protocol settings. Apple's Files app needs SMB 2.0 or later, so there are two ways to get it wrong:

The server's maximum is SMB1. Old NAS boxes and some routers only speak SMB1. Back on iOS 13, one user fixed it by enabling SMB2 on their NAS. A TechRepublic writer had to raise their Synology's maximum to SMB3 before it connected.
The server is locked to SMB3 only. In an Ask Different question covering iOS 15.3 to 18.2, a Samba server restricted to SMB3 logged NT_STATUS_NOT_SUPPORTED during negotiation. The accepted answer allowed some older dialects during the handshake. Another answer says iOS negotiates SMB3_02, so on Samba you'd set server min protocol = SMB3_02 rather than SMB3 (which means the newest dialect, SMB3_11).

I should flag a conflict here: the accepted answer says Files uses SMB3_11 on iOS 18, and the other answer says SMB3_02. I don't know which is right for current iOS. On your own Samba server, run smbstatus while the iPhone is connected and it shows the dialect in use.

The safe setting: Maximum SMB3, Minimum SMB2. That's Synology's own recommendation, and it avoids both problems above.

What about turning SMB1 back on?

Some people did. In the Apple Community thread "Can't Connect to SMB share from iOS 17" (218 "Me too"), an iPadOS 17.2 user lowered their Synology's minimum to SMB1 to get connected. That looks like it was working around an iOS 17 bug that was reportedly fixed in 17.2.1. Don't do it. SMB1 is old and insecure, Synology "strongly advise[s] against" it, and the iPhone doesn't need it. Update iOS instead.

"There was a problem connecting to the server": address and network

Try the IP, then the name. Synology's help writes the two forms as smb://192.168.1.100 and smb://MyNAS.local. If one works, use it.
Check you copied the right IP. On Windows, ipconfig lists every adapter. Use the Wi-Fi or Ethernet one, not a VPN or vEthernet adapter.
Check the firewall. SMB uses port 445 (Synology also lists 137 to 139). A Windows PC on a Public network profile blocks it.
Check the server isn't blocking your phone. Synology's Auto Block can block an IP after too many failed sign-ins. See the Synology checklist.
Don't use QuickConnect or a public hostname. Synology says SMB doesn't work over QuickConnect addresses. Away from home you need a VPN and the VPN address.

"Permission denied" and "Invalid argument"

I only found one thread for each of these, so treat the causes as likely rather than certain. "Permission denied" (reported with a Synology) points at the account: check your user's permissions on the share and sign in as Registered User. "Invalid argument" was reported when connecting as Guest, so try a real account. If you can connect but can't save, that's a different problem: see the read-only share fix.

"An unexpected error occurred": an iOS bug

iOS 18.7.9 broke Files SMB connections for a lot of people: an "unexpected error", then the share showing as "Empty" on retry. According to the person who started the Apple Community thread, iOS 18.7.10 fixed it. That mattered for phones like the iPhone XR that can't run iOS 26. Something similar hit iOS 17 and was reportedly fixed in 17.2.1. If you're on an affected version, update.

Clean up Recent Servers

Files keeps the servers you've connected to under Recent Servers on the Connect to Server screen. Old entries can cause trouble. One Ask Different user got "a file with the same name already exists" because two saved servers had shares with the same name. To remove one, tap the (i) next to it and choose Remove, then add the server again fresh. Doing this after you've changed server settings is a good habit anyway.

Where SMBDrop fits

Disclosure: I make SMBDrop. It's an iPhone app for sending photos, videos and files to SMB shares, £9.99 once with no subscription or account. It connects to the same server, so the server-side fixes on this page (SMB version range, firewall, permissions, Auto Block) apply to it too. It won't connect to an SMB1-only server either. It does let you set a custom port, and after you've entered the address and signed in, Find Shares lists the shares so you don't have to guess names. It needs Settings → Privacy & Security → Local Network turned on, as all third-party apps do to reach your home network.

If you get connected but folders won't open, see "Content Unavailable".

FAQ

Does the iPhone Files app support SMB1?

No. The Files app needs SMB 2.0 or later. If your server only speaks SMB1, enable SMB2 or SMB3 on it rather than trying to make the iPhone use SMB1.

What SMB settings should my server use for an iPhone?

Set the maximum protocol to SMB3 and the minimum to SMB2. That's Synology's recommendation. If you want an SMB3-only Samba server, people report that server min protocol = SMB3_02 works where SMB3 alone does not.

What does Operation not supported mean when connecting to SMB on iPhone?

A protocol mismatch is one reported cause: the server only speaks SMB1, or it's locked to the newest SMB3 dialect. Check the server's minimum and maximum SMB protocol settings.

How do I remove a server from Recent Servers in the Files app?

Open Connect to Server, tap the (i) next to the server under Recent Servers, and choose Remove. Then add it again with the current address and account.

More guides

Try SMBDrop

Send original photos, videos and files from your iPhone straight to your own SMB share. One purchase, no account, no subscription.

£9.99 once · no subscription · iOS 17+