#MACOS SERVER FILE SHARING IOS HOW TO#
#MACOS SERVER FILE SHARING IOS MAC#

uses the server name as the share name, which solves issue 2 single-handedly.Feedback - particularly if it improves security - is welcome. Here's an example smb.conf that works well with iOS files.app and strives to be reasonably secure (SMB is a well known attack vector!). For example, by including the host name, which can be stubbed as %h if you like to keep your config files standardized.Ī sample smb.conf that works for the iOS files.app For issue 2, locate the name of the share (placed between brackets in my example ) and change it to smth unique.For issue 1, you'll want to ensure server min protocol (typically found in the section) is set to SMB2.Logon to your SMB server and run sudo -i to access root privileges.The below procedure and example are based on Ubuntu but they should work similarly on other *NIX/*BSD derivatives (and NAS) that use Samba as the SMB server software, albeit possibly with different paths/filenames etc:

How to adjust a SMB server's config to solve both issues In my case, the standard configuration of my servers was to call them smth like smbshare attempting to access more than one server with the same share name, causes the issue, which looks like a bug in files.app IMHO (the share names should be qualified by the server name). Solution 2: ensure unique SMB share name across serversĪ better workaround is to ensure that the name of the SMB share is unique across the connections stored/remembered in your files.app. This may be a workaround in case you don't have access to the server config although you'll only be able to access one of the 'clashing' servers/shares at a time, which could be frustrating. Issue 2 Solution 1: delete old/clashing 'server' connectionĭeleting a connection to a previous server that provides a share with the same name (files.app -> main menu (.) -> connect to server -> (i) -> Remove) solves the issue. This requires adjusting the server's configuration (see below).

Issue 1Īlthough files.app appears to perform most of its traffic over the SMB3 protocol, some initial connection activity only appears to work if the server accepts SMB2 requests. In order to fix both issues optimally, you'll need (admin) access to your SMB server configuration although a workaround exists for Issue 2 if you don't. Question: are there any workarounds/fixes to these files.app 'quirks'? The same issue was raised on Apple's forums with a fair number of 'me too's' but no workable solution has been provided. I've hit this issue a number of times, typically when migrating from an old SMB server to a new one. Issue 2: 'The file couldn’t be saved because a file with the same name already exists' Server logs report smth along the lines of: smbd_smb2_request_error_ex: idx status || at. This happens with a server configured to restrict itself to SMB3 and above (SMB3, after all, has 'only' been around since 2012). Issue 1: 'The operation couldn't be completed: Operation not supported' This is with iOS 15.3 (latest as of writing) these issues were definitely also experienced with older iOS versions. Ultimately it may not be the right thing for you, just my 2 cents.I've encountered at least two frustrating issues upon trying to connect to a new SMB server with the iOS files.app (main menu (.) -> connect to server). I’ve been very impressed with Synology since I started using them several years ago. The difference is that they are trying to improve these features year after year.Īll the drive bays in a Synology can be configured into several pools of disks so that you can have several separated RAID volumes all working under one roof.Īnd yeah if you’re looking at 10Gb LAN in the future they are well geared for it. The current state of the Server App alone is enough to put most people off.Ĭompare that to companies like Synology and QNAP etc.

One thing that stopped me from coming back to Mac servers is that Apple move further and further away from providing adequate server functionality each year. If you’re talking about SSD RAID then yeah ignore what I mentioned about the HDD’s.ĭuoModo looks like an interesting option.

#MACOS SERVER FILE SHARING IOS HOW TO#

#MACOS SERVER FILE SHARING IOS MAC#

Macos server file sharing ios