[cups.general] Upgrade to 1.6.2 breaks DNS-SD print server setup

Dennis Leeuw dleeuw at made-it.com
Thu Apr 11 01:24:53 PDT 2013


Hi all,

We have the following setup:

A CUPS 1.4.3 print server running on Ubuntu server in a server network. 
A couple of Mac OS X (and Windows and Linux) clients in different 
networks around the organisation and they all need to access the same 
print server. To make Bonjour printing work we added DNS-SD entries to 
our DNS server. This worked fine until the upgrade to Mac OS X 10.8.3.

The DNS-SD setup to support the printers looks like this:
b._dns-sd._udp.domain.nl domain name pointer domain.nl.
lb._dns-sd._udp.domain.nl domain name pointer domain.nl.

_ipp._tcp.op.domain.nl domain name pointer printer01._ipp._tcp.domain.nl.
_universal._sub._ipp._tcp.domain.nl domain name pointer 
printer01._ipp._tcp.op.domain.nl.
_cups._sub._ipp._tcp.domain.nl domain name pointer 
printer01._ipp._tcp.domain.nl.

printer01._ipp._tcp.domain.nl descriptive text "txtvers=1" "qtotal=1" 
"rp=printers/printer01" 
"adminurl=ipp://ipp.domain.nl.:631/printers/printer01" "product=(hp 
LaserJet 4350)" "ty=HP LaserJet 4350" "note=room 120" "Priority=50" 
"pdl=application/postscript" "Transparent=F" "Binary=F" "TBCP=F" "URF=none"

printer01._ipp._tcp.domain.nl has SRV record 0 0 613 ipp.domain.nl.
printer01._ipp._tcp.domain.nl has address 123.123.123.123
ipp.domain.nl has address 456.456.456.456

With Mac OS X up till 10.8.2 (CUPS 1.6.1) all worked fine. Users could 
select the printer via the printing panel, the PPD file got fetched from 
the CUPS servers and everybody was (more or less) happy.
With the upgrade to Mac OS X 10.8.3 and CUPS 1.6.2 this seems to be 
broken some how. In the printing panel the printer can be selected and 
installed, but when the user tries to print  the print-job-dialog says: 
"Printing - The printer is not responding"

Looking at the settings on localhost:631 web interface the Defaults say 
media=na_letter_8.5x11in instead of media=iso_a4_210x297mm which should 
be the default from the PPD on the print server.
The printing-panel in the pre-10.6.2 situation says at Kind the name 
from the PPD, where in the 10.6.2 situation it reports "Generic 
PostScript Printer"
tcpdump on the print server records a SYN packet from the client and an RST

So it seems that the new cups is not getting the PPD and can, somehow, 
not connect to the print server. What I also noticed is a lot of SNMP 
connections from the Mac OS X clients to the print server (but these are 
blocked in the print server firewall).

A telnet from the client to port 631 works.

Running:
dns-sd -B _ipp._tcp .
on the client shows:
date_string Add 3 0 domain.nl _ipp._tcp printer01

I am probably overlooking something, but what? Can someone point me in 
the right direction?

Thanks,

Dennis Leeuw





More information about the cups mailing list