Re: Any reports of IOS 18.79/Files failure to connect to samba? (all prior IOS versions worked)

Rowland Penny via samba <[email protected]> Thu, 21 May 2026 09:21:42 +0100
Newsgroups gmane.network.samba.general
Message-ID <[email protected]>
On Tue, 19 May 2026 17:14:55 -0500
David C Rankin via samba <[email protected]> wrote:

> Samba folks,
> 
>    One thing I use samba for (in standalone mode) is to allow smb 
> connection from IOS/Files app to hosts on the local network. This has 
> worked like clockwork for the past several years.
> 
>    Recently Apple release IOS 18.79 to address a myriad of AI
> discovered exploits over the past several weeks. Following the update
> I can no longer connect to samba from the iPhone.

If nothing has changed on the Samba side and it no longer works after
changes on the iOS side, then it sounds like an iOS problem.

> 
>    I have opened a discussion with Apple as well:
> 
> https://discussions.apple.com/thread/256299931

After reading that link, it seems that the one person that answered
replied to the wrong question, they seem to think you have a problem
with your router.

> 
>    The basic config to allow users to reach their homes share on each
> PC is:
> 
> $  testparm
> Load smb config files from /etc/samba/smb.conf
> Loaded services file OK.
> Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility
> fallback)
> 
> Server role: ROLE_STANDALONE
> 
> Press enter to see a dump of your service definitions
> 
> # Global parameters
> [global]
>          disable netbios = Yes
>          dns proxy = No
>          map to guest = Bad User
>          printcap name = cups
>          security = USER
>          server string = %h Samba %v
>          idmap config * : backend = tdb
>          cups options = raw
>          hosts allow = 192.168.6.
>          vfs objects = fruit streams_xattr
> 
> 
> [homes]
>          browseable = No
>          comment = Home Directories
>          read only = No
> 

Nothing wrong with that smb.conf file.

>    Nothing has changed here. I have tested against 4.23.6 (openSUSE 
> Tumbleweed) and 4.24.2 (Archlinux), there is no difference in
> behavior.
> 
>    I don't pay much attention to the log when things are working, and 
> from what I can tell, the logs show the same information they always 
> have (4.23.6 and 4.24.2 show the same other than version no., likely
> not helpful, but included for completeness):
> 
> log.samba-dcerpcd:  (4/23 connection OK, 5/19 connection failed)
> 
> <snip>
> [2026/04/23 01:45:06.222643,  0] 
> ../../source3/rpc_server/rpc_host.c:2889(main)
>    samba-dcerpcd version 4.23.6-git.466.1a6b75cb208SUSE-oS16.9-x86_64 
> started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2025
> [2026/05/19 02:46:16.636259,  0] 
> ../../source3/rpc_server/rpc_host.c:2889(main)
>    samba-dcerpcd version 4.23.6-git.466.1a6b75cb208SUSE-oS16.9-x86_64 
> started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2025
> <snip>
> 
> 
> log.rpcd_classic:
> 
> <snip>
> [2026/04/23 01:45:06.379795,  0] 
> ../../source3/rpc_server/rpc_worker.c:1148(rpc_worker_main)
>    rpcd_classic version 4.23.6-git.466.1a6b75cb208SUSE-oS16.9-x86_64 
> started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2025
> [2026/05/19 02:46:16.785453,  0] 
> ../../source3/rpc_server/rpc_worker.c:1148(rpc_worker_main)
>    rpcd_classic version 4.23.6-git.466.1a6b75cb208SUSE-oS16.9-x86_64 
> started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2025
> <snip>
> 
> 
> log.rpcd_winreg:
> 
> <snip>
> [2026/04/23 01:45:06.444744,  0] 
> ../../source3/rpc_server/rpc_worker.c:1148(rpc_worker_main)
>    rpcd_winreg version 4.23.6-git.466.1a6b75cb208SUSE-oS16.9-x86_64
> started. Copyright Andrew Tridgell and the Samba Team 1992-2025
> [2026/05/19 02:46:16.851342,  0] 
> ../../source3/rpc_server/rpc_worker.c:1148(rpc_worker_main)
>    rpcd_winreg version 4.23.6-git.466.1a6b75cb208SUSE-oS16.9-x86_64
> started. Copyright Andrew Tridgell and the Samba Team 1992-2025
> <snip>
> 
>    What it does show is the iPhone is connecting with samba host, but 
> it's just not doing whatever it used to do to establish a connection.

ER, no it doesn't, unless you snipped the relevant data, the logs just
show the Samba deamons starting up.

> 
>    Let me know what else I can provide, and I'm happy to do it. You
> will need to include a link to show me how to set lever-10 debug
> again if that is needed. (samba just works for me, so it's been years
> since I had to debug). My guess is this is an Apple created issue
> where their attempts to correct a bug has had side-effects on the smb
> connection, but given it involves a connection to samba, I also
> wanted to inquire here to see if this has been confirmed.

Setting the log level to 10 is easy, just add 'log level = 10' to the
global part of the smb.conf file and reload the config or restart Samba.

Doing that might not help, you may have to resort to using wireshark to
see what is going on when you attempt to connect from iOS to your share.

Rowland



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba