Hello all, I've got an HP 4200 with a processing job message and a flashing data light. I've swapped out the network card but it made no difference. If you power the printer on with the data cable disconnected the printer will go to ready, but as soon as you plug in the cable the message comes back and the printer is locked up. It will print a config page and a jet direct page with the data cable disconnected. I have tried a cold reset and an nvram reset but no change. None of the customers other printers are affected. Anybody have any ideas???
HP 4200
Collapse
X
-
It could be a corrupt job in the print queue. I don't know why, but sometime the server will repeatedly try to send the same corrupt print job. If you can't clear the print queue, there is a relatively easy way to reset the spooler.
Here's another thing to try: Load another print driver, and assign a different unique IP address and see if that corrects your problem.If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
I literally had this problem yesterday. It turned out it was a print spooler running on windows XP. Have the Admin restart that service. I agree with the previous post. I always try a crossover cable to a laptop to verify its not the printer... then I leave it in the customers hands to fix!
Thanks...Comment
-
Few Suggestions
I would try the following things:
1.) Replace the network card with a 620 HP jetdirect card. The cards memory buffer could be corrupt.
2.) Restart the print spooler or contact a computer professional to advise.
3.) Check the print queue on the computer that is sending jobs to the 4200. Sometimes jobs are too much for the memory of the computer and do not transfer from the computer to the printer in a timely matter. Watch the print queue on the machine to see if this is true. This would account for processing job issues.
DanielComment
-
Been away from HP's for a bit now... so not sure if the industry is still plagued by this issue... but heaven help you if you tried two different JetDirect 615's. I have had them lock up machines, give no display and just disappear from the configuration page. I agree with last poster... 620 or even an old trusted 610 (maybe from a LJ 4000 or such). Outside of this, it does sound like bad info/job getting resent. May need to actually move printer to another network (like depot repair at your own shop, maybe?). Trust me, I have had to do it in the past to prove to the customer it was their 'perfect' network and not the printer. Please post results.The glass maybe half full, but less is more...
Printer + Fax + Copier = Jack Of Many Trades,
but Master Of None
Color Copier = Not A Color Printer
InkJet MFP = Not A Fax Machine
B/W Copier = Not A Press
Finisher = Deal Closer (salesman, not accessory)
Copier Tech = Admin's Stress Ball (Scapegoat)Comment
-
tech1224
-
tech1224
-
CannonHPtech makes a good point. The 615 cards are crap. I have had them kill a printer just by being inserted, even though there was no conection going into the card. A bad 615 card won't do the same thing every time, sometimes it just makes you think your printer has lost it's mind.The greatest enemy of knowledge isn't ignorance, it is the illusion of knowledge. Stephen HawkingComment
-
At the suggestion of our supplier I've been replacing all the 615s with 610s or 620s. I haven't replaced a NIC card in two months.If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
It could be a corrupt job in the print queue. I don't know why, but sometime the server will repeatedly try to send the same corrupt print job. If you can't clear the print queue, there is a relatively easy way to reset the spooler.
Here's another thing to try: Load another print driver, and assign a different unique IP address and see if that corrects your problem.
I had several times a jamed IP problem, mainly on mainframe computers that an IP address had to be replaced and we couldn't reset it.Comment
Comment