My macOS network Time Machine backups broke around 3/28/2026, perhaps when I installed 25.10.2 update. The backups would fail saying that it could not connect to my truenas server e.g. “could not connect to truenas.local”
I installed 25.10.3 - Goldeye update yesterday. Today, when I started to troubleshoot the TM issue, I noticed that it had successfully completed the network backup. Just to be sure, I kicked off a manual backup, which worked fine.
1 Like
commit 0a7310dd6d13e775af0e63d541af847a2a22599e (tag: TS-25.10.3, origin/release/25.10.3.1, origin/release/25.10.3, origin/release/25.10.2.2)
Author: Andrew Walker <awalker@ixsystems.com>
Date: Thu Mar 12 12:50:43 2026 -0500
NAS-140077 fix idmap_ad when private krb5.conf disallowed (#523)
This commit skips steps to generate a private krb5.conf file
if explicitly disallowed by the smb.conf file.
commit 399c0e16402ae37fd4156a25b51f1a24e0f7748f (tag: TS-25.10.2.2, tag: TS-25.10.2.1, tag: TS-25.10.2, origin/stable/goldeye, origin/release/25.10.2.1, origin/release/25.10.2, release/25.10.2.2)
No code changes related to time machine between 25.10.2 and 25.10.3. It sounds more likely that you were having some mDNS related issue on the network (since you were failing to find a .local address). These can sometimes be shaken loose by restarting avahi or the SMB service (that will force a new service registration message to be generated which can prompt the server to re-appear to macos).
1 Like