iOS/iPadOS can't access SMB share (authentication failed in log)

[leana8959]

Hello,

Since a couple of months ago, I can no longer connect to my SMB share via my iPhone (iOS 16.3.1) or iPad (iPadOS 16.3.1).
My TrueNAS machine is running version `TrueNAS-13.0-U4`
I've checked the log, it seems like there's an authentication error, of which I don't understand the cause.

What I've tried
I can connect to the same SMB share via my MacBook Pro (macOS 13.2.1) without any issue.
I wondered if it's due to an incompatibility after a TrueNAS upgrade, so I selected the boot partition of the older version and rebooted. That didn't fix it, sadly.

Reproduction of error
There are two different messages, depending on the address I connect to.
The TrueNAS server in question is located at `10.0.0.20` in my LAN.
If I try to connect to the address `smb://10.0.0.20` and fill out the credentials, I get an error message, "You entered an invalid username or password for the server."
If I try to connect to the address `smb://10.0.0.20/data` (that is, with the name of the share) and fill out the credentials, I can see the share in the folder but going inside the share I see the error message "Content Unavailable The folder contents could not be displayed because of an unknown error."

Log
MacBook Pro (authentication success)

Code:

{
    "timestamp": "2023-03-20T10:40:49.644690+0100",
    "type": "Authentication",
    "Authentication": {
        "version": {
            "major": 1,
            "minor": 2
        },
        "eventId": 4624,
        "logonId": "0",
        "logonType": 3,
        "status": "NT_STATUS_OK",
        "localAddress": "ipv4:10.0.0.20:445",
        "remoteAddress": "ipv4:10.0.0.10:62398",
        "serviceDescription": "SMB2",
        "authDescription": null,
        "clientDomain": "MAINFRAME",
        "clientAccount": "leana",
        "workstation": "MBP",
        "becameAccount": "leana",
        "becameDomain": "TRUENAS",
        "becameSid": "S-1-5-21-3414699754-3168776633-1485921531-1005",
        "mappedAccount": "leana",
        "mappedDomain": "MAINFRAME",
        "netlogonComputer": null,
        "netlogonTrustAccount": null,
        "netlogonNegotiateFlags": "0x00000000",
        "netlogonSecureChannelType": 0,
        "netlogonTrustAccountSid": null,
        "passwordType": "NTLMv2",
        "duration": 8960
    }
}

iPad (authentication failed)
The two different error code previously described correspond to the same error message on the server side.

Code:

{
    "timestamp": "2023-03-20T10:41:21.678296+0100",
    "type": "Authentication",
    "Authentication": {
        "version": {
            "major": 1,
            "minor": 2
        },
        "eventId": 4625,
        "logonId": "0",
        "logonType": 3,
        "status": "NT_STATUS_WRONG_PASSWORD",
        "localAddress": "ipv4:10.0.0.20:445",
        "remoteAddress": "ipv4:10.0.1.12:55569",
        "serviceDescription": "SMB2",
        "authDescription": null,
        "clientDomain": "",
        "clientAccount": "leana",
        "workstation": "MOBILE",
        "becameAccount": null,
        "becameDomain": null,
        "becameSid": null,
        "mappedAccount": "leana",
        "mappedDomain": "",
        "netlogonComputer": null,
        "netlogonTrustAccount": null,
        "netlogonNegotiateFlags": "0x00000000",
        "netlogonSecureChannelType": 0,
        "netlogonTrustAccountSid": null,
        "passwordType": "NTLMv2",
        "duration": 97185
    }
}

It seems like there's quite some information missing in the authentication request when I try to connect via iPad.
Is there any work around of this? Is this issue caused by the SMB implementation used in the iPad?

Here's my `/etc/local/smb4.conf` if it comes in handy.

Code:

#
# SMB.CONF(5)           The configuration file for the Samba suite
# $FreeBSD$
#


[global]
        dns proxy = No
        aio max threads = 2
        max log size = 5120
        load printers = No
        printing = bsd
        disable spoolss = Yes
        dos filemode = Yes
        kernel change notify = No
        directory name cache size = 0
        server multi channel support = No
        nsupdate command = /usr/local/bin/samba-nsupdate -g
        unix charset = UTF-8
        log level = 1 auth_json_audit:3@/var/log/samba4/auth_audit.log
        obey pam restrictions = False
        rpc_daemon:mdssd = disabled
        rpc_server:mdssvc = disabled
        enable web service discovery = True
        logging = file
        server min protocol = SMB2_02
        unix extensions = No
        restrict anonymous = 2
        server string = Welcome to the Matrix
        fruit:nfs_aces = No
        bind interfaces only = Yes
        netbios name = mainframe
        netbios aliases =
        server role = standalone
        workgroup = WORKGROUP
        idmap config *: backend = tdb
        idmap config *: range = 90000001-100000000
        registry shares = yes
        include = registry

Thank you, I appreciate your help!

 

[leana8959]

Hello,

I figured out why! It's because I wasn't authenticating with the right password.
I'm really sorry for those who took the time to read my question, the answer was right under my nose this whole time...

Turns out I don't type what I thought I was typing on my Mac, it was the right password, but I was thinking the wrong password. (talking about muscle memory at its worst...)
Have a good day !