Unix client printing via Windows print server to Canon printer -- "Local Downlevel Document"

We have an app on a Solaris 10 (sparc) server that sends print jobs to a Windows print server.  We have a variety of printer models and manufacturers.  Most of them work just fine for both Unix and Windows print jobs (HP, Konica, etc.)

When we send print jobs to a Canon iR C3480, we see an object in the Windows print spool called "Local Downlevel Document".  It disappears after a second.  There is no indication on the printer itself anything is happening.  

This happens whether we send a job from the Unix app or from the Solaris OS level itself, running a command like  
/usr/ucb/lpr -P testpr09 /export/freehog/printer_test

We've tried to send both Unix app and OS level print jobs when this printer is on both a Windows 2003 print server and a Windows 2008 print server.  Doesn't matter.

It works fine for pure Windows PC print jobs.  We have some other printers that act the same way too -- the job just disappears, usually with "Local Downlevel Document" messages.  

Any suggestions where to go next for troubleshooting this?
Hank LieuranceAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jwhite109Commented:
I would start by making sure all printers are using the same driver type (PCL, PS, GDI). I am unsure what type of print driver that Canon uses (Konica Minolta, Sharp, HP expert), but that is generally the most likely issue.

If they are all using PCL (most likely) check version from there (5c, 5e, 6).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Hank LieuranceAuthor Commented:
Switching the affected printers to the PCL5 driver worked.  A couple were on PS drivers and a couple were on UFR II.  Thanks for the help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Printers and Scanners

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.