Thomas-M

Q: iOS File Share apps unable to access File Shares since 10.11.5

Since updating my server to OS X 10.11.5 & Server 5.1.5 I've run in to this problem.

 

Macs still access server file shares flawlessly as they always have - no problems there.

 

However multiple apps iOS apps (iPhone & iPad) for accessing network shares return the same message "Connection Failed With Error: Failed To List Files" when attempting to connect to my server shares, these apps worked fine until recent updates. Not limited to iOS 9.3.2 as I've tried from older devices and still receiving the same errors.

 

I use the same credentials on my Macs as i do on the iOS apps, never been a problem there.

 

Now the only thing that does work is Guest shares on the server, if i connect as a Guest user on the iOS apps, i am able to access guest accessible shares on the server, but thats it. All authenticated access is being rejected - even the admin account - which all works from my Macs..

 

However, if i access my MacBook (no server app ruling on that machine and running 10.11.5) file shares, they are able to access everything as per normal.

 

Where do i start?

Mac mini (Late 2012), OS X Server

Posted on May 18, 2016 8:46 AM

Close

Q: iOS File Share apps unable to access File Shares since 10.11.5

  • All replies
  • Helpful answers

Previous Page 2
  • by Warwick Teale,

    Warwick Teale Warwick Teale May 30, 2016 12:20 AM in response to ebaauw
    Level 3 (588 points)
    May 30, 2016 12:20 AM in response to ebaauw

    Thanks heaps!, this resolved these failures with apps at iOS 9.3.2 and OSX 10.11.4 that access SMB files from a osx server shared file system.


    Such iOS 9.3.2 apps such as Filebrowser from Stratospherics and GoodReader that utilise SMB access will fail with a password prompt on client side (iOS). Logging in server side is typically:


    May 30 13:34:56 macmini-04-server smbd[23907]: Server requires signing while bound to unauthenticated Directory Service

    May 30 13:34:57 macmini-04-server smbd[23907]: Connection failed, signing required but no session key

    May 30 14:30:52 macmini-04-server smbd[23907]: signing is required, but 10.0.99.2 is not signing

    May 30 14:30:52 macmini-04-server smbd[23907]: session_setup_transact: activate_signing returned status 0xc000a000: status

     

    Also remember to restart the SMB daemon:

    sudo serveradmin stop smb

    smb:state = "STOPPED"

    smb:status = 0

    sudo serveradmin start smb

    smb:state = "RUNNING"

    smb:status = 0

    sudo serveradmin fullstatus smb

    smb:state = "RUNNING"

    smb:logPaths = _empty_dictionary

    smb:currentConnections = 1

    smb:currentThroughput = 0

    smb:servicePortsAreRestricted = "NO"

    smb:servicePortsRestrictionInfo = _empty_array

    smb:failoverState = "NIFailoverNotConfigured"

    smb:logging = "NO"

    smb:guestAccess = "NO"

    smb:setStateVersion = 2

    smb:startedTime = ""

    smb:readWriteSettingsVersion = 1

     

    Warwick

    Hong Kong

  • by Warwick Teale,

    Warwick Teale Warwick Teale Jun 15, 2016 3:32 AM in response to zeumann
    Level 3 (588 points)
    Jun 15, 2016 3:32 AM in response to zeumann

    Hi Zeuman, in this regard we have been impacted by the Statospherix iOS Filebrowser.app. Thanks for adding this information. I can concur that adding the target hosts netbios name, or the its OD realm /  (or its AD equivalent) or host's workgroup name causes the SMB authentication to occur here and is successful. 


    In our case the SMB connections being authenticated again an Open Directory / LDAP realm on OSX 10.11.5 with Server.app V5.1.


    For Stratospheric's iOS 9.3 Filebrowser.app the authentication string is in ye olde windows format as GROUPNAME\user-account . Example:

    VFXREALM\freelance09


    Thanks again.


    Warwick

    Hong Kong

Previous Page 2