Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-2990: How to troubleshoot authenticated printing issues on Mac OS X.

Mac & PC Management Service ,  

17 January,18 at 11:26 PM

Applies to: All versions of Centrify DirectControl on Mac OS X 10.11 and higher


Printers have been added into a Mac system according to one of the methods described in the KB:
However attempts to print documents are failing when using the cdcsmb:// protocol (authenticated printing).

Printers added under regular non-authenticated protocols work fine.

What are the troubleshooting steps to figure out why authenticated printing is not working?


Authenticated printing relies on a series of steps to flow correctly:
  1. User sends a document to print queue.
  2. Document is passed into the cdcsmb process.
  3. cdcsmb looks at:
    • Sockets in /var/centrifydc/adprint/
    • Relevant credentials to send to printer.
  4. Once credentials and sockets have been found, everything is passed to the adprintd process to send to printer.
  • If any part of this flow breaks, then print jobs will fail.

To generate debug logs for print failures, please use the following steps:
  1. Login to the system as Local Admin
  2. Open the following file for editing: /etc/centrifydc/centrifydc.conf 
  3. Add the following lines to the bottom of the file: 
    • log.cdcsmb: DEBUG 
    • log.adprintd: DEBUG
  4. Logout of the Local Admin account and login as the AD user. 
  5. Open the Terminal and enter the following commands: 
    • login local admin username
    • sudo adreload
    • sudo /usr/local/share/centrifydc/bin/centrifydc restart 
    • sudo /usr/local/share/centrifydc/bin/addebug clear 
    • sudo /usr/local/share/centrifydc/bin/cdcdebug on
    • (Replace "local admin username" with the actual username of the Local Admin of the Mac)
  6. Start up a network trace:
    • (If the Mac is connected via Ethernet)
    • sudo tcpdump -i en0 -s 0 -w /tmp/print.pcap
    • (If the Mac is connected via WiFi)
    • sudo tcpdump -i en1 -s 0 -w /tmp/print.pcap
    • (For further info on the above commands, see: ) 
  7. Try to print a document and let it fail. 
  8. Take screenshots of any error messages displayed.
  9. Stop the network trace and enter the following commands: 
    • klist > /tmp/klist.log 
    • sudo /usr/local/share/centrifydc/bin/cdcdebug off 
    • sudo /usr/local/share/centrifydc/bin/cdcdebug pack AD_Username 
    • adquery user -A AD_Username > /tmp/adquery.log
    • (Replace AD_Username with the actual username of the affected AD user) 
  10. Send any screenshots and the following files to Centrify Support:
    • /var/centrify/tmp/cdcdebug.tar.gz (or /tmp/cdcdebug.tar.gz )
    • /tmp/print.pcap 
    • /tmp/klist.log 
    • /tmp/adquery.log 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.