On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote: > wooledg:~$ cat /etc/debian_version > 11.6 > wooledg:~$ lpstat -l -e > Canon_LBP712C_UFR_II_ permanent > ipp://localhost/printers/Canon_LBP712C_UFR_II_ > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/
This is a print queue, set up using Canon drivers. > Canon_LBP712Cdn_db_c0_d3_ network none > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/ This is not a print queue. CUPS has discovered the printer via mdns/DNS-SD and enumetated it. It should be seen with avahi-browse -rt _ipp._tcp avahi-browse -rt _uscan._tcp (I would find that data useful for my records). It can be printed to with lp -d "Canon_LBP712Cdn_db_c0_d3_" FILE Where the job physically ends up is outside the scope of CUPS. Let's assume the printer you ar interested in is not being multicast. It exists at 10.76.172.100. Let us guess that the resource to access on the printer is ipp/print. This is a pretty good guess because most vendors use it nowadays. Its URI will be ipp://10.76.172.100/ipp/print Execute lpadmin -p mycanonprinter -v URI -E -m everywhere Test printing with lp -d mycanonprinter /etc/nsswitch.conf -- Brian.
