From: dan@djph.net   
      
   On 2024-05-17, philo wrote:   
   > On 5/17/24 8:14 AM, Dan Purgert wrote:   
   >> On 2024-05-17, philo wrote:   
   >>> For the 2nd time now, I followed the instructions exactly.   
   >>> There were two separate options.   
   >>   
   >> Wait, are you using the CUPSWrapper tool/script, or *just* the driver?   
   >>   
   >> Because it's pretty easy to mess up the CUPSWrapper script ... IIRC, it   
   >> shows all *potential* queues that the printer "should(tm)" support, but   
   >> it's just a generic list and doesn't correspond to what that printer has   
   >> been configured to support from within the printer's own control   
   >> panel / web-interface.   
   >>   
   >>   
   >   
   >   
   >   
   > Here is all that I can tell you   
   >   
   >   
   >   
   > Configurations provided by Brother that did NOT work.   
   >   
   > Four possibilities   
   > The first one  was automatically installed and if I delete it, simply   
   > re-appears   
   > implicitclass://[...].local/   
   > dnssd://[...]._ipp._tcp.local/   
   > ipp://[...]._ipp._tcp.local/   
   > lpd://BRNB42200DDC4F8/BINARY_P1   
   >   
   > (Brother HL-L2370DW series, driverless, cups-filters 1.28.15)   
      
   ALL of these are mDNS / autodetect / zeroconf printers, and won't have a   
   driver set ("driverless" is kind of key there).  The only one that   
   actually defines a print queue is the last one (lpd://), though the   
   device name might not resolve properly if you tried using it. The other   
   three are just "kick it to the printer and pray"; which, let's face it,   
   won't actually work.   
      
   In short, the mDNS / DNS-SD information being presented by the printer   
   is incomplete or otherwise wrong.  The only thing that'd correct this   
   would be either:   
      
     (A) Updated firmware from Brother OR   
     (B) You correct it via the printer's webUI   
      
   Alternatively, stop / remove cups-browsed so that your PC stops picking   
   up these bad entries from the printer in the first place.   
      
   >   
   >   
   > What worked:   
   >   
   > the socket configuration I simply copied from the working Samsung   
   > auto-detect   
   >   
   >   
   > socket://192.168.2.103:9100   
      
   Yes, because you're not using mDNS AND have a driver defined. Likewise,   
   using ipp or lpd with this IP address (and the proper print queue -->   
   "Binary_P1") would likely also work.   
      
      
   --   
   |_|O|_|   
   |_|_|O| Github: https://github.com/dpurgert   
   |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)