On Thursday 10 Mar 2016 13:31:36 stan wrote:
On Thu, 10 Mar 2016 10:08:00 +0000
Jonathan Allen <jonathan(a)barumtrading.co.uk> wrote:
> I agree - the print job never seems to leave the laptop. There is
> nothing that I can see in the server logs that shows an access or
> attempt to access the printers apart from the discovery messages
> which all seem normal. The printer itself is fine and can be used by
> other workstations on the LAN without problems.
It sounds like it is a communication problem. Is there anything
different about the firewall or printer configuration compared with one
of the workstations that work? How about the permissions or context
of files and directories?
Can you manually reach the printer over the network? I'm not sure how
to check that, but it seems pertinent.
Just a thought, but when I had a similar
problem it was because there was a
print job at the head of the queue that was crashing a filter and restarting
the queue just repeated the problem until I got into /var/spool/lpd (I think
it was) and manually removed the spool files.