Can't delete print jobs on an HP printer que

On a XP workstation computer, we can't print to one network printer (we can to other network printers).

The printer we can't print to, has a number of jobs stuck in the print que - from other workstations.  They do not show these jobs, and they can print fine.

Nobody can delete these jobs.

I have uninstalled the network printer on this workstation and reinstalled it - no luck.

What do do next?
egaschoAsked:
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.

GRiTechCommented:
I've found a useful utility for completely resetting the local print spooler to default, cleaning all drivers\registry\ports etc from the local machine.  Might be useful for problem machine with strange printing problems.  Also might need to reboot to finish clearing everything.
 
This tool is part of the xp/2003 resource kit - cleanspl.exe

Try running this and see if it cures it.  You'll need to set up all printers on the workstation zapped.

Could also try a cold reset on the printer just for good measure.

Hope this helps
Cheers
0
patrickabCommented:
It is generally not a good idea to allow any network user to delete anything off the print queue. It is usually set so that people can only delete their own work from the queue.
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
GRiTechCommented:
Totally agree patrick, however if a printadmin uses cleanspl out of the resource kit it can give a totally clean PC to start afresh, just to make sure theres not a corrupt dll or something.

Cheers
G
0
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

patrickabCommented:
GRiTech - Thanks for that - patrickab
0
patrickabCommented:
Most generous as I didn't solve anything really - patrickab
0
patrickabCommented:
Most generous as I didn't solve anything really - patrickab
0
GRiTechCommented:
Yes but your information probably set egascho off on the right track......;o) I guess we'll never know unless egascho tells us more - Cheers G
0
egaschoAuthor Commented:
Sorry didn't get back to you all.  The problem ended up being a print driver / issue and something to do with our changing our server IP addresses to the standard addressing scheme (which we did recently). I uninstalled the printers completely from servers and all machines, then reinstalled - now everything is working.  The XP 2003 tools "cleanspl.exe" did zap the printers on the workstation I first had trouble with.  But in the meantime everyone had problems, so I started from strach.

Thanks guys.
0
GRiTechCommented:
Thanks for the feedback, glad you got it sorted - G
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.