![]() |
| |||
| Why is it that I can use lpr and lpq to communicate with a print server, but not lprm? That is, lpr -H 192.168.0.105 works. And lpq -h 192.168.0.105 works. But lprm -h 192.168.0.105 comes back with "lprm: Unable to contact server!". (I'm running SuSE 10.3, in case that matters.) |
| |||
| strnbrg wrote: > Why is it that I can use lpr and lpq to communicate with a print > server, but not lprm? > That is, > lpr -H 192.168.0.105 > works. And > lpq -h 192.168.0.105 > works. But > lprm -h 192.168.0.105 > comes back with "lprm: Unable to contact server!". > > (I'm running SuSE 10.3, in case that matters.) Hello: I wonder what "# lpstat -h 192.168.0.105" might produce? I also wonder if all your above commands use "CUPS"? Did you recently update your version of CUPS? -- 1PW |
| |||
| strnbrg <strnbrg59@gmail.com> writes: >Why is it that I can use lpr and lpq to communicate with a print >server, but not lprm? >That is, > lpr -H 192.168.0.105 >works. And > lpq -h 192.168.0.105 >works. But > lprm -h 192.168.0.105 >comes back with "lprm: Unable to contact server!". Probably because it is lprm -P 192.168.0.105 They have clearly linked to lpr and lpq to the cups lp and lpstat but have not linked lprm which is a lpd command. >(I'm running SuSE 10.3, in case that matters.) |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |