I've got samba setup and working with my printer on the server machine.
I'm using cups on the client and lprng on the server. I don't use cups on
the server because cupsd daemon crashes immediately - always (i've tried
reinstalling). Using client side printer drivers to process the printer job.
Sending text (ie, a plain text file) to the printer works fine. If I try
sending any sort of graphics - anything than is not plain text (including
printing from KWord etc, as well as bmp, png gifs etc etc), the printer
prints a load of *- it printers the graphics as though as its text -
much like if you try viewing the contents of a binary file on the console.
The printer is fine if I print non text files on the server machine, but
not if I try printing remotely.
I can't see what the problem is: the client PC (windows and linux) uses its
printer drivers to process the print job, and then all that needs to to
happen is the data is sent to the server ready for printing - without any
need for server side print drivers. (ie, raw printing)
The printer command in smb.conf is:
print command = lpr -P %p -l %s
above: -l = -o raw
for raw printing
print command = lpr -P %p -o raw %s -r
but the -o raw stops the printer from printing - the job doesn't even show
on the print queue.
Thanks for any help