From: philo@privacy.net   
      
   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://Brother_HL_L2370DW_series%40BRNB42200DDC4F8.local/   
      
   dnssd://Brother%20HL-L2370DW%20series._ipp._tcp.local/?uuid=e324   
   000-80ce-11db-8000-b4220   
      
   ipp://Brother%20HL-L2370DW%20series._ipp._tcp.local/   
      
      
   lpd://BRNB42200DDC4F8/BINARY_P1   
      
      
      
   (Brother HL-L2370DW series, driverless, cups-filters 1.28.15)   
      
      
   What worked:   
      
   the socket configuration I simply copied from the working Samsung   
   auto-detect   
      
      
   socket://192.168.2.103:9100   
      
   (Brother HL-L2360D series, using brlaser v6)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)