On Mon, Apr 19, 2010 at 5:49 PM, Kevin.Beaumont
> Vinod Nadiadwala wrote:
>> i am using thinstation 2.2 with 70+ thin-clients with windows 2003
>> terminal services, i am having HP laserjet 1000, 1020, 1010, 1022,
>> P1007, while Laserjet 1010 & 1022 printer is working perfectly, but
>> other printers like LJ 1000, 1020, P1007 printers are not working
> I've been looking at this myself today with a HP LaserJet P1005 printer
> which falls in exactly the same area by the looks of it - i.e. it needs
> firmware sending to the printer before it will work.
> After a bit of investigation I got the firmware (it's a binary file) and I
> could manually cat it to /dev/usb/lp0. Then I loaded the printer driver
> onto the Windows Server 2003 Terminal Server and connected using rdesktop.
> Then I could print.
> However! The manual cat'ing of the USB firmware is obviously an issue, but
> the bigger show stopper was the Print Spooler service on the server was
> sometimes crashing or hanging, which caused problems were users sessions
> when logging out (and back in) would hang. I would have to restart the
> spooler to fix the user sessions, and to be able to print again.
> I checked with HP and they have a Terminal Services/Citrix support matrix in
> PDF. Basically, the long story short is these printers don't use PCL or
> Postscript, but instead use "Host based" drivers, i.e. firmware. The
> reality is this doesn't work very well (and in the case of the P1005 at
> least, isn't supported in Terminal Services). Rather than trying to fix the
> problem in Thinstation I will probably consult the matrix to find printers
> which are supported in Terminal Services and have PCL or Postscript drivers,
> and replace the printers.
Troublefree Linux printing = Postscript. Everything else is trouble
and waste of time.
My 2 cents.
Operator of the Danish TS-O-Matic.
- a light, full featured linux based thin client OS