[Samba] Any reports of IOS 18.79/Files failure to connect to samba? (all prior IOS versions worked)

[David C Rankin]

On 5/23/26 1:35 AM, Rowland Penny via samba wrote:
> On Fri, 22 May 2026 17:48:22 -0500
> David C Rankin via samba <samba at lists.samba.org> wrote:
> 
>> On 5/21/26 4:51 AM, David C Rankin wrote:
>>> IOS 18.79 SMB Connect Attempt/FAIL
>>> https://paste.opensuse.org/pastes/fef2b8f16419
>>>
>>> SUMMARY
>>>
>>> I've summarized all the "error" messages below. I don't know if
>>> they are actual errors, or just attempts to try connection features
>>> I don't use (like all the 'open' fails in a strace as it checks
>>> every component of the file path)
>>>
>>> There are two types of errors (look like normal fails in a strace,
>>> but Greek to me). They are (tdbsam_getsampwrid), first four, then
>>> (ad_get_internal), the rest, which would make sense since I don't
>>> have any AD?
>>>
>>>
>>
>> Can anybody confirm that the level-10 errors listed are simply normal
>> and don't have anything to do with IOS/Files not making the smb
>> connection to my samba host? I don't want to say they are unrelated
>> until I know they are unrelated.
>>
>> If I know the tdbsam_getsampwrid and ad_get_internal errors in the
>> level-10 are not related to the failure of Files to connect as it
>> always has before the IOS 18.79 update - then I can take that
>> information to Apple in my support thread and push further there.
>>
>> As it is, I don't know conclusively what those errors mean, so I'm
>> left not knowing for sure if they are related or unrelated.
>>
>> Full level-10 for the connect attempt is linked above, the errors are
>> summarized in the previous post in this thread.
>>
>> Thanks for any guidance here.
>>
> 
> I have examined the level 10 log file and nothing jumps out.
> 
> I will say it again, if nothing has changed on the Samba side and it
> worked until there was an iOS update, but no longer works after the iOS
> update, pure logic would suggest it is something to do with the iOS
> update.
> What did they change ?
> 

Follow up. Apple fixed the issue in the 18.7.10 release. (original 
report and confirmed fixed)

https://discussions.apple.com/thread/256299931?login=true&sortBy=rank&answerId=262075139022

Would have been nice if Apple could have at least acknowledged the issue 
and that a fix was in work instead of speculating on the cause....

Thanks again for taking a look Rowland.


-- 
David C. Rankin, J.D.,P.E.