Windows 2003 Terminal Server Printing issues - "system job" stays in queue all the time

hi guys,

i have 2003 terminal server misbehaving it's printing. working has since started cause problems know can work properly. here symptoms:

i have several pcs connecting server same type of printer - canon lbp3100. rdp redirecting print jobs these printers. in print queue of each of these printers job called: "system job" status "sent printer" pages n/a , size of 44 bytes. job seems blocking other print jobs being deleted queue. jobs print, remain "sent printer"  and queue fills up. printing slow.

i have changed permissions on spool drive allow users full rights , allowed anonymous have same permissions "everyone" in local security policies.

i've updated drivers latest ones available canon's website.

if disable bi-directional support, "system job" queues, prints , re-queues endlessly user changing after each "printing" whoever logged in. is, print user 1, print user 2, user 3 , user 1 again.

i've deleted drivers , re-installed them on terminal server , desktop pcs.

interestingly have 2 network printers each user has available them , these not share same fault local (re-directed) printers seem have. seem indicate problem re-directed printers don't know go here.

does have advice?

 

thanks - angus

hi,

not print drivers compatible terminal services.  based on have written print driver not compatible , should removed server.

the lbp3100 host-based printer, , such not candidate use terminal server.  host-based printers use large amounts of cpu , bandwidth when compared printer natively has ability understand pcl/ps/etc. , rasterize job internally.  other common thing host-based printers drivers work under ts, if @ all.

one potential alternative purchase third-party ts universal print driver solution, or upgrade server 2008 r2 , use rd easy print.  these upd products allow use wide variety of printers otherwise not work under ts without loading print drivers on server (except upd driver).  downside of ts upd upfront cost, may high if have small number of users and/or incompatible printers.  example, may cheaper purchase new printers compatible.

note: if have rd easy print or third-party upd there still small percentage of printers may not work properly.

printers work ts natively understand pcl or ps , have small, no-frills whql-certified drivers.  nice thing printer understands pcl or ps if manufacturer's driver has bug can substitute generic pcl/ps driver shipped windows.

-tp

Windows Server  >  Remote Desktop Services (Terminal Services)