Mac clients can’t print to AD-shared printer — SMB/Kerberos & CUPS fixes
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
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.
| Symptom | Likely cause | Quick 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)
- Verify Kerberos:
klist(renew withkinit), ensure NTP time sync. - Clear Keychain SMB/cifs entries for the server; reconnect with domain account.
- Add printer by smb://server.domain/queue or IPP Everywhere by IP; prefer FQDN.
- Install vendor driver/PPD; set finishing options in CUPS.
- If issues persist, Reset printing system and rebuild the queue.
Optional: advanced checks
- Confirm DNS/SPN correctness and reverse lookup for the print server.
- Validate SMB signing and NTLM policies; avoid guest access.
- For managed fleets, deploy URIs and drivers via Jamf / mobileconfig for consistency.
Sources
- Apple — Kerberos (klist/kinit) on macOS
- Apple Platform Deployment — Deploying printers (CUPS/IPP)
- Microsoft — SMB security (signing, NTLM)
Filed under: Printer won’t print
Related articles
- Printer won’t print after I changed Wi-Fi — what should I check first?
- Printer won’t print after I installed a new router — what do I check first?
- Printer won’t print my medical forms online — what do I check first?
- Printer won’t print bank forms online — the Print button works, but nothing comes out
- Printer won’t print from a website — I click Print and nothing happens
- Printer won’t print a PDF correctly — why is it cutting off or coming out blank?
- My printer ignores my print settings — why is it printing the wrong way?
- My printer won’t print black ink — but everything else prints. What’s wrong?