Hi! We can definitely work through a TrueNAS SCALE ADS print auth fail, especially when it mentions Kerberos.
To avoid guessing, I need a quick picture of your setup:
• Which version of TrueNAS SCALE are you running, and is the server joined to Active Directory / ADS as an SMB domain member?
• Are Windows clients printing directly to a printer shared from TrueNAS over SMB, or to a Windows print server that spools to a share on TrueNAS?
• What exact error do you see on the client side — “Access denied”, “0x0000001B”, “0x00000709”, or a pop-up asking for credentials over and over?
• In the TrueNAS SCALE logs (log.smbd, log.winbindd or journalctl), do you see messages like NT_STATUS_LOGON_FAILURE, KRB5KRB_AP_ERR_TKT_EXPIRED, SPNEGO failed, or “print_auth_fail”?
Once I know that, I’ll walk you step-by-step through checking the ADS join, Kerberos keytab, time sync, SPNs and SMB printer share permissions so printing works again with domain accounts.
Customer
We’re on TrueNAS SCALE 24.x joined to our AD domain. File shares work with Kerberos SSO fine. The issue is with a printer shared from TrueNAS via SMB (CUPS on TrueNAS, then shared as an SMB printer). When users print from Windows, the job shows “Error – printing” and on the TrueNAS side I see print auth failed and NT_STATUS_LOGON_FAILURE. It mentions kerberos_error: KRB5KRB_AP_ERR_TKT_EXPIRED or sometimes “no ticket”. File shares from the same box are okay, just ADS print auth fails.
That helps a lot — classic TrueNAS SCALE ADS Kerberos print auth fail pattern where SMB file access works but spoolss / printer auth is broken.
Typical reasons you see NT_STATUS_LOGON_FAILURE or KRB5KRB_AP_ERR_TKT_EXPIRED only on printing:
• The TrueNAS SCALE host is joined to ADS, but the Kerberos keytab doesn’t contain the right HOST / cifs SPNs for the print host name users connect to.
• Time skew between TrueNAS, the domain controller and the Windows clients is big enough that Kerberos tickets are treated as expired when the print job is created.
• The printer share is forcing NTLM or guest in a way that conflicts with your Kerberos-only security settings (server min protocol, client ipc signing, etc.).
• ADS / winbind can resolve users for SMB shares, but the spoolss service can’t map them to valid domain SIDs when it tries to create spool files and ACLs.
We’ll start by confirming the ADS join and Kerberos tickets are clean on the TrueNAS SCALE side, then we’ll check the SMB printer share and permissions.
Customer
In TrueNAS SCALE, the Directory Services → Active Directory page shows status “Connected”. getent passwd on the shell returns domain users, and file shares are accessible with Kerberos SSO. I haven’t touched the Kerberos settings manually, just joined ADS from the web UI. Time should be synced via NTP to the same DCs. The only problem is that printing to the TrueNAS SMB printer fails auth while browsing the share is okay.
Good, that means basic ADS / winbind is healthy. Let’s zoom in on Kerberos and the SPNs TrueNAS is using for SMB / printing.
Step A — Confirm time sync and Kerberos tickets
Open a shell on the TrueNAS SCALE box (either SSH or the web console) and check:
1) Time: run date on TrueNAS and compare to your DC — the difference should be < 5 minutes (ideally < 1 minute).
2) Kerberos test as a domain user:
• kinit SOMEUSER@YOURDOMAIN.LOCAL
• klist — confirm you get a valid TGT and service tickets, not “ticket expired”.
Step B — Check the keytab and SPNs TrueNAS is using
Still on TrueNAS SCALE, run (if available):
• net ads testjoin — should return “Join is OK”.
• net ads keytab list — confirm entries like host/truenas.yourdomain.local and cifs/truenas.yourdomain.local exist.
If the cifs/ SPN is missing or only exists for a different hostname than the one Windows clients use for the printer, Kerberos print auth can fail with NT_STATUS_LOGON_FAILURE even though file shares partially work.
Customer
Time looks fine (few seconds off). net ads testjoin says “Join is OK”. net ads keytab list shows host/TRUENAS.domain.local and cifs/TRUENAS.domain.local. Windows users are connecting to the printer via \\truenas.domain.local\OfficePrinter, so that matches. Still getting print auth failed with NT_STATUS_LOGON_FAILURE in the SMB logs when a user prints from a domain-joined Windows 11 machine.
Perfect, SPNs match the FQDN, so we’re likely dealing with how the SMB printer share is configured on TrueNAS SCALE and how ADS permissions are applied.
Step C — Check the SMB printer / spool share
In the TrueNAS SCALE UI:
1) Under Sharing → SMB, look at the share backing your printer spool directory (often something like print$ or a dedicated dataset).
2) Confirm that the share is set to use AD permissions (not Unix / guest only), and that “Enable ACL” is on for the dataset.
3) On the dataset ACL itself, make sure Domain Users (or the groups that should print) have at least modify (write) permissions so they can create spool files.
Step D — Test SMB access with the same user, but to the spool path
From a Windows client using a user that fails to print:
• Browse to the share backing the printer (for example \\truenas.domain.local\print$ or the dataset path).
• Try creating and deleting a test folder. If you get “Access denied” or a credential prompt, you’ve found a mismatch between ADS ACLs and what the print subsystem expects — that can trigger Kerberos print auth failures even though basic SMB looks okay in other paths.
Customer
The printer spool share is using an SMB share on a dataset with ACLs. Domain Users have modify rights there and can create folders when browsing via Explorer. So permissions look okay. Logs show lines like “kerberos_kinit_password DOMAIN\user@REALM failed: Preauthentication failed” followed by NT_STATUS_LOGON_FAILURE (print_auth_fail) when the job is submitted. Again, only TrueNAS SCALE ADS print auth fails — normal file access with the same user works.
Those log lines are gold. They suggest that when spoolss tries to impersonate the user for printing, the Kerberos pre-auth or cached credentials are wrong, so the DC returns PREAUTH_FAILED and Samba reports NT_STATUS_LOGON_FAILURE specifically for print.
A few things to look at in this situation:
Step E — Ensure SMB is using the same domain controllers and DNS
• On TrueNAS SCALE, confirm that DNS servers are the AD DCs and that /etc/krb5.conf / Kerberos settings point to the right realm.
• If you recently changed domain controllers or migrated to new DCs, restart directory services and SMB so TrueNAS SCALE gets fresh Kerberos details.
Step F — Refresh the ADS join and Kerberos keytab
In the TrueNAS UI:
• Temporarily disable Active Directory, wait for it to stop, then enable it again so TrueNAS regenerates its Kerberos keytab and winbind state.
• If you previously joined with an account that changed password, re-join ADS using a current domain admin/service account.
Often just refreshing the ADS join and keytab clears stale Kerberos secrets that affect printer auth while leaving normal SMB mostly functional.
Customer
I disabled and re-enabled ADS from the TrueNAS SCALE Directory Services page and re-entered a domain admin account. net ads testjoin still says OK. After restarting SMB, users can print one or two jobs, then a bit later we start seeing NT_STATUS_LOGON_FAILURE again on printing while file shares stay fine. Feels like Kerberos tickets expiring or something similar.
That “works for a while then fails” behaviour is very typical of Kerberos ticket lifetime or host/alias mismatch issues.
Step G — Check which hostname clients actually use for printing
• Confirm in Windows Printer properties that clients use exactly \\TRUENAS.domain.local (or the host matching your cifs/ SPN).
• If some clients use a short name (e.g. \\TRUENAS) or a CNAME alias (e.g. \\nas-print), but the Kerberos SPN only exists for the FQDN, you can get intermittent Kerberos print auth failures while SMB falls back to NTLM for normal shares.
Ideally, register SPNs for all names you use (FQDN and short name) on the computer account in AD (cifs/TRUENAS, cifs/TRUENAS.domain.local), or standardise on the FQDN only.
Step H — Align ticket lifetimes and NTP
• Check your domain’s Kerberos policy (default ticket lifetime / renewal). Very aggressive or mismatched settings can trigger KRB5KRB_AP_ERR_TKT_EXPIRED mid-session.
• Make sure TrueNAS SCALE is using the same NTP source (usually the DC) as the rest of the domain and that it keeps time in sync automatically, not just at boot.
Once hostnames and time are solid, Kerberos should stop randomly expiring tickets for printing.
Customer
Yeah, some clients were added as \\TRUENAS and others as \\TRUENAS.domain.local. We standardized on the FQDN and re-added the printer. That seems to help a bit, but I still get occasional auth failures from a couple of users. When that happens, trying to “Connect” the printer again prompts them for credentials instead of using Kerberos SSO.
Good catch on the hostnames. The remaining cases sound like Windows occasionally falling back to NTLM or using cached local credentials instead of domain Kerberos when talking to the TrueNAS printer.
A few clean-up steps often stabilize that:
Step I — Clear Windows cached credentials for the NAS
On an affected Windows client:
• Open Control Panel → Credential Manager → Windows Credentials.
• Remove any saved entries for TRUENAS or TRUENAS.domain.local.
• Log off and back on so the user gets a fresh Kerberos ticket and the printer connection uses domain SSO.
Step J — Ensure SMB / Kerberos policy fits your AD
In TrueNAS SCALE SMB service settings:
• Avoid overly restrictive combinations like “Kerberos only” if your domain still expects some NTLM talk for printer enumeration.
• Match settings like server signing, client ipc signing, and client ntlmv2 auth with your domain security policy so Windows clients don’t fall back to non-domain credentials for printing.
After this, most environments stop seeing the intermittent TrueNAS SCALE ADS print auth fail errors, and printers behave like normal AD printers.
Customer
We cleared stored credentials and reconnected the printers using the FQDN for a few test users. So far, print jobs are going through and no NT_STATUS_LOGON_FAILURE in the logs for them. If this crops up again, is there a “nuclear” option to completely redo the ADS / Kerberos integration on TrueNAS SCALE without reinstalling the whole box?
There is a “clean slate” approach if things ever get messy again, and it often cures stubborn
TrueNAS SCALE ADS Kerberos auth issues for both SMB and printers.
Step K — Full AD / Kerberos refresh (when you have a maintenance window)
• In TrueNAS SCALE: leave the domain (disable AD and remove the computer account from AD Users & Computers after noting the shares).
• Reboot the TrueNAS SCALE host so winbind/smbd start fully fresh.
• Re-join ADS using a dedicated
service account or a domain admin, letting TrueNAS generate a new
Kerberos keytab with proper SPNs.
• Re-check
net ads testjoin,
net ads keytab list, and
kinit/
klist before bringing shares back online.
• Finally, re-add the SMB printer share and reconnect printers on the clients using the FQDN only.
Most admins don’t need this drastic step once hostnames, time sync, SPNs and cached credentials are cleaned up — but it’s there if you ever want to fully reset
TrueNAS SCALE ADS / Kerberos behaviour.
If you ever want someone to watch logs in real time while you submit a print job, just
start a chat with an expert and we’ll walk through it live.
Customer
Understood. Standardizing on the FQDN, refreshing the ADS join, and clearing cached credentials seems to have fixed the TrueNAS SCALE ADS print auth fail Kerberos issue for now. If it comes back, I’ll plan a full re-join window like you described. Thanks for the detailed explanation!
Anytime! Quick recap: when a
TrueNAS SCALE ADS print auth fail error shows
NT_STATUS_LOGON_FAILURE or Kerberos errors, first verify the
ADS join, NTP time sync and Kerberos keytab / SPNs. Then check that the printer’s SMB / spool share uses the right ACLs for domain users and that Windows clients connect with the same hostname the SPNs are registered for. Finally, clear cached Windows credentials and align SMB / Kerberos policies so clients stop falling back to non-domain auth. If you ever want someone to sanity-check your
TrueNAS SCALE AD / Kerberos configuration, just
open a chat and an expert will walk through it step by step.
Why TrueNAS SCALE ADS print auth fails with Kerberos errors
Most TrueNAS SCALE ADS print authentication failed cases come down to a few core issues: Kerberos tickets, SPNs, hostnames and permissions. When TrueNAS SCALE is joined to Active Directory (ADS), SMB file shares may work over Kerberos while the spoolss printer service fails with NT_STATUS_LOGON_FAILURE or GSSAPI / Kerberos errors. If the cifs/ service principal in the keytab doesn’t match the hostname clients use for printing, or if there’s time skew between TrueNAS and the domain controllers, Kerberos treats the tickets as invalid or expired and you see KRB5KRB_AP_ERR_TKT_EXPIRED or PREAUTH_FAILED in logs.
Another common reason for TrueNAS Kerberos print auth fail is inconsistent SMB configuration: forcing Kerberos in the domain but exposing printer shares that expect NTLM or guest access, or using a CNAME / short name that has no SPN registered. On top of that, if the printer’s SMB share or backing dataset doesn’t have correct AD ACLs for Domain Users to create spool files, Samba might log print_auth_fail as soon as it tries to impersonate the user. Separating these layers — ADS join, DNS / hostnames, Kerberos keytab, SMB printer share and Windows client credentials — is the key to finding the real cause instead of randomly re-adding the printer.
How to test if your TrueNAS SCALE Kerberos printing is really fixed
To confirm a TrueNAS SCALE ADS Kerberos print auth issue is resolved, use a simple validation sequence. First, from the TrueNAS shell, run net ads testjoin and net ads keytab list to make sure the server is still correctly joined to Active Directory and that the cifs/hostname SPN is present. Use kinit and klist with a test domain user to verify Kerberos tickets are issued and not immediately expired. Then, from a domain-joined Windows client, browse to the NAS using the printer’s FQDN (for example \\truenas.domain.local), create a test folder on the spool share, and confirm that works without prompting for extra credentials.
Next, remove and re-add the TrueNAS SMB printer on the Windows client using the same FQDN that the SPNs are registered for. Submit a small test print job and watch the TrueNAS log.smbd and log.winbindd (or journal) in real time. A healthy configuration will show Kerberos-based connections and the job moving to “printed” status without NT_STATUS_LOGON_FAILURE or print_auth_fail messages. If file shares work but printing still fails, re-check SPNs, hostnames, ADS ACLs on the spool dataset, and any cached Windows credentials for the NAS.
TrueNAS SCALE ADS print auth fail — quick Kerberos troubleshooting tips
Focus on ADS join, SPNs, time sync and printer share ACLs before changing everything else.
Fast path: verify the TrueNAS SCALE Active Directory join with net ads testjoin, confirm the cifs/hostname SPN exists in the keytab, and check that TrueNAS and your domain controllers share the same NTP time source. Standardize Windows printer connections on the FQDN that matches that SPN, and make sure the SMB spool share uses AD ACLs that grant Domain Users write access. Finally, clear cached Windows credentials and reconnect the printer so Kerberos SSO is used consistently. If you still see NT_STATUS_LOGON_FAILURE or Kerberos errors in the log, a clean AD re-join and keytab regeneration on TrueNAS SCALE usually resolves stubborn Kerberos print auth issues.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your TrueNAS version, AD schema, domain security policy and printing environment, please consult a verified expert on Whizz-Tech or your vendor’s official documentation before making changes.
Why does TrueNAS SCALE show ADS print auth fail with NT_STATUS_LOGON_FAILURE?
This usually means Kerberos authentication for the printer share is failing even though the Active Directory join appears OK. Common causes are missing or mismatched cifs/hostname SPNs in the TrueNAS SCALE Kerberos keytab, time skew between the NAS and domain controllers, or clients connecting with a hostname that doesn’t match the SPN. In these cases, file shares may still work while the spoolss printer service logs NT_STATUS_LOGON_FAILURE or print_auth_fail when users print.
How do I fix Kerberos print auth fail on TrueNAS SCALE joined to ADS?
First verify the ADS join using net ads testjoin and confirm the cifs/hostname SPN exists in the keytab with net ads keytab list. Check that TrueNAS, your DCs and clients use the same NTP time source. Standardize printers so Windows connects using the FQDN that matches the SPN, ensure the SMB spool share has AD ACLs granting Domain Users write access, and clear any cached Windows credentials for the NAS. If the problem persists, re-join ADS from the TrueNAS UI to regenerate the Kerberos keytab.
Can DNS or hostnames cause TrueNAS SCALE Kerberos print authentication to fail?
Yes. If clients print to \\TRUENAS or to a CNAME alias like \\nas-print while the Kerberos SPN is only registered for cifs/TRUENAS.domain.local, you can see intermittent Kerberos print auth fail errors. Always either register SPNs for every hostname you use, or standardize on a single FQDN that matches the SPN for SMB and printing.
When should I completely re-join TrueNAS SCALE to Active Directory?
If you consistently see NT_STATUS_LOGON_FAILURE or Kerberos errors for both printing and SMB file shares, or if the Kerberos keytab and SPNs look wrong even after restarts, it’s often faster to leave and re-join ADS. Remove the computer account from AD, reboot TrueNAS SCALE, then join the domain again from the UI so it generates a fresh Kerberos keytab and updates SPNs. After that, re-test SMB and printing with a small group of users before rolling changes to everyone.