On Fri 01 Mar 2019 at 12:34:45 +0000, mick crane wrote: > On 2019-03-01 12:24, Brian wrote: > > On Fri 01 Mar 2019 at 12:21:05 +0000, Brian wrote: > > > > > On Fri 01 Mar 2019 at 12:09:16 +0000, mick crane wrote: > > > > > > > On 2019-03-01 11:49, Brian wrote: > > > > > > > > > > on client PC > > > > > > $ lpstat -t > > > > > > scheduler is running > > > > > > system default destination: HP_LaserJet_4000_Series > > > > > > device for HP_LaserJet_4000_Series: socket://10.0.0.108 > > > > > > > > > > This is not a connection to the server. socket://... indicates a > > > > > direct > > > > > connection to the printer. > > > > > > > > with CUPS server network cable plugged in > > > > "enscript file" > > > > prints > > > > with CUPS server network cable unplugged > > > > "enscript file" > > > > hangs, does not print > > > > > > Communication with a remote CUPS server is with IPP over port 631. > > > socket://... is over port 9100. > > > > Just to be clear: cupsd doesn't listen on port 9100. > > I'm presuming that the "lpstat -t" result is the CUPS server saying how it > is connected to the printer
Much more likely. I took "client PC" to mean the machine you were printing from. Overall, quite an interesting problem. I would never have considered using the lpr package, so have learned something. Then again, I've never found a use for the lpr command. -- Brian.
