Printer troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: macOS Sonoma/Sequoia, CUPS/SMB, Printers, Networking, AD integration

Fix “Mac can’t print to AD-shared printer” — repair SMB/Kerberos auth & CUPS queue

Technician avatar Technician
Hey! Let’s sort out why macOS can’t print to an AD-shared printer. Typical causes are SMB authentication issues (Kerberos ticket, NTLM, keychain), driver vs AirPrint mismatch, or a broken CUPS queue. Are you connecting via smb://printserver/queue from a Windows print server, or using IPP/LPD by IP? We’ll check Kerberos, server permissions, and rebuild the queue if needed.
Customer
Macs joined to AD can browse the share but jobs stay “On hold (authentication required)” or fail with “Unable to connect to printer on server”. Windows users print fine.
Technician avatar Technician
Got it. On macOS, AD-shared printing fails most often because:
• No valid Kerberos ticket (or time skew) → SMB auth prompts or “hold for authentication”.
• Server requires SMB signing / NTLMv2 only, while the Mac uses cached old creds in Keychain.
• Driver mismatch (Windows Type 3/4 share) vs AirPrint/IPP Everywhere on the Mac; or missing vendor PPD.
• Broken local CUPS config (printers.conf, stale queue) or blocked by Content Security Policy in management profiles.
We’ll verify tickets, clear Keychain entries, add the printer with the right protocol, and, if needed, reset the printing system.
Customer
We use smb://print01/HP-Floor2 from a Windows Server 2019 print server. Macs are AD-bound. Where do I check Kerberos and Keychain?
Technician avatar Technician
Step 1 — Kerberos & time
1) Open Terminal → run klist. If you don’t see a TGT for your realm, run kinit yourADuser or log out/in.
2) Ensure NTP is in sync: systemsetup -getusingnetworktime and systemsetup -getnetworktimeserver. Time skew > 5 minutes breaks Kerberos.
3) Test SMB with Kerberos: smbutil statshares -a after connecting. If it shows “SMB Signing Required”, we’re fine.
Customer
klist shows no tickets. After kinit it prints once, then asks again later.
Technician avatar Technician
Step 2 — Keychain & correct path
• In Keychain Access → search for cifs/smb entries for print01. Delete stale saved passwords so macOS uses your Kerberos ticket.
• When adding, use the SMB URL format smb://print01.domain.local/HP-Floor2 (FQDN avoids DNS suffix issues).
• If the server enforces NTLMv2 only or legacy guest access is disabled, anonymous connections fail — that’s expected.
Customer
Should we use AirPrint/IPP instead of SMB share from the server?
Technician avatar Technician
Choose the most compatible path:
• If the printer supports IPP Everywhere / AirPrint, add by IP using ipp://printerIP/ipp/print or http://printerIP/ipp — this bypasses Windows driver packaging.
• If you must use the Windows AD-shared queue, stay with SMB but install the vendor PPD/driver on the Mac (or “Generic PCL/PS” if compatible).
• For older fleets, LPD/LPR sometimes works better than SMB.
Customer
We installed using AirPrint before. Now some jobs lose stapling and duplex options.
Technician avatar Technician
Install the vendor driver & set CUPS options
1) Get the latest macOS driver/PPD (Sonoma/Sequoia) for your model.
2) Re-add the printer with Use: choose the installed driver (not AirPrint).
3) Open http://localhost:631 (enable with cupsctl WebInterface=yes) → Set Default Options for finisher, stapler, duplex, trays. This ensures job options survive through the AD-shared path.
Customer
Some Macs still prompt for a password every time. Anything else to check?
Technician avatar Technician
Stability checklist
• Confirm DNS resolution both ways: A & PTR for print01. Kerberos needs proper SPNs and reverse lookup.
• Ensure SMB signing policies match (server “required” is OK; Mac supports it).
• If you deploy via Jamf/mobileconfig, set the printer URI exactly (FQDN) and disable saving plaintext passwords.
• Remove any “Allow guest access” experiments; modern macOS + AD disables guest printing by design.
Customer
What if the local printing system is corrupted on one Mac?
Technician avatar Technician
Reset the printing system (macOS)
1) System Settings → Printers & Scanners → right-click in the list → Reset printing system… (removes queues/drivers).
2) Delete /Library/Printers vendor folders for stale packages, then reinstall the latest driver.
3) Reboot the Mac → add the printer via smb://print01.domain.local/HP-Floor2 or IPP with the correct driver.
Customer
We use Papercut on the server. Any special notes for release queues?
Technician avatar Technician
For Papercut / pull-print
• Use the vendor’s Papercut PPD on macOS, not AirPrint.
• Keep the server queue name identical in your deployment profile.
• If jobs stall, check the Mac’s /var/log/cups/error_log for NT_STATUS_ACCESS_DENIED or auth loops — that’s usually Kerberos/Keychain. Need help reading logs or pushing a Jamf profile? Open the chat and I’ll walk you through live.

Quick answer: the accepted fix

Accepted fix for Mac can’t print to AD-shared printer: get a valid Kerberos ticket and sync time → clear stale Keychain SMB entries → add the printer via smb://server/queue (FQDN) or IPP Everywhere with the correct driver/PPD → configure options in CUPS. Reset the printing system if the queue is corrupt.


Why macOS fails to print to an AD-shared queue

Modern macOS enforces secure SMB and Kerberos. If time is out of sync, DNS/SPN is wrong, or cached Keychain passwords override tickets, jobs sit on hold. Using AirPrint/IPP Everywhere without the vendor PPD may also remove finishing features. Standardize on FQDN paths (smb://printserver.domain/queue), correct drivers, and healthy CUPS to avoid repeats.

How to verify the fix

After changes, print a test page from TextEdit. In http://localhost:631, ensure your options (duplex/staple) are set. Run klist to confirm an active ticket, and smbutil statshares -a to see signing/auth method. No more “Hold for Authentication” or repeated password prompts indicates the SMB/Kerberos path is healthy.

Pro tips — Kerberos, SMB & CUPS checklist

Lock down the path from the Mac to your Windows print server.

Use FQDNs and sync NTP; keep Kerberos tickets valid; clear old Keychain SMB passwords; prefer IPP Everywhere when features match, else deploy the vendor PPD/driver; set finishing in CUPS; confirm SMB signing policies; and for fleets, push consistent printer profiles via Jamf or a mobileconfig.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.

Expert will respond in minutes

We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or expensive consults. Membership can save you significant time and money each month.

FAQ

Why does macOS say “On hold (authentication required)” for an AD-shared printer?

Usually missing Kerberos ticket, wrong Keychain SMB credentials, DNS/SPN mismatch, or server policy requiring SMB signing. Clear Keychain entries, renew ticket (kinit), and add via FQDN.

AirPrint or vendor driver for AD-shared printers?

IPP Everywhere/AirPrint is simplest, but for stapling/finishers install the vendor PPD/driver and configure options in CUPS.

What URI should I use?

Prefer smb://printserver.domain.tld/queue for Windows shares or ipp://printerIP/ipp/print for direct IPP. Avoid NetBIOS-only names.

How do I reset the printing system on a Mac?

System Settings → Printers & Scanners → right-click → Reset printing system…, then reinstall the driver and re-add the printer.

Can guest access print to AD queues?

No. Guest/anonymous SMB is blocked in most AD environments. Use Kerberos or NTLMv2 with domain credentials.

Common Mac & AD-shared printing problems and quick fixes
SymptomLikely causeQuick fix
On hold (authentication required) No Kerberos ticket; stale Keychain creds Renew kinit, delete SMB entries in Keychain, add using FQDN
Prints but missing stapling/duplex AirPrint generic driver Install vendor PPD/driver; set options in CUPS
Can’t connect to Windows share SMB signing/NTLM policy or DNS issue Match policies; verify A/PTR; use smb://server.domain/queue
Jobs fail on one Mac only Corrupt CUPS/driver cache Reset printing system; reinstall driver; re-add queue

Step-by-step (macOS)

  1. Verify Kerberos: klist (renew with kinit), ensure NTP time sync.
  2. Clear Keychain SMB/cifs entries for the server; reconnect with domain account.
  3. Add printer by smb://server.domain/queue or IPP Everywhere by IP; prefer FQDN.
  4. Install vendor driver/PPD; set finishing options in CUPS.
  5. If issues persist, Reset printing system and rebuild the queue.

Optional: advanced checks

  1. Confirm DNS/SPN correctness and reverse lookup for the print server.
  2. Validate SMB signing and NTLM policies; avoid guest access.
  3. For managed fleets, deploy URIs and drivers via Jamf / mobileconfig for consistency.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant