BostonTony
11-23-2005, 02:20 AM
Hi there.
LaserJet 5M printer, been a good workhorse for many years (relatively light use), but has now developed a problem.
When a job is sent to the printer (it's networked), the printer says "Processing job..." and never leaves that state.
Yeah, I know what you're thinking -- JetDirect card is sick, right? Yeah, I thought that, too. But I swapped a different (and newer, actually) JetDirect card in from another printer, and the problem persists. Furthermore, the printer cannot print test pages or anything else. Always, I get the same sort of result. If I try to print a font list, say, it says it's printing the font list, but nothing prints and it sits in that state forever.
Where should I go from here? Would a burned out fuser, say, cause this problem (printer waiting for it to come up to temperature and it never does)? I would think that sort of thing would be caught by self-test at power-up, but I don't know. Or is it more likely to be a logic board thing? RAM?
Any thoughts, or suggestions for a way to approach further troubleshooting? Thanks!
LaserJet 5M printer, been a good workhorse for many years (relatively light use), but has now developed a problem.
When a job is sent to the printer (it's networked), the printer says "Processing job..." and never leaves that state.
Yeah, I know what you're thinking -- JetDirect card is sick, right? Yeah, I thought that, too. But I swapped a different (and newer, actually) JetDirect card in from another printer, and the problem persists. Furthermore, the printer cannot print test pages or anything else. Always, I get the same sort of result. If I try to print a font list, say, it says it's printing the font list, but nothing prints and it sits in that state forever.
Where should I go from here? Would a burned out fuser, say, cause this problem (printer waiting for it to come up to temperature and it never does)? I would think that sort of thing would be caught by self-test at power-up, but I don't know. Or is it more likely to be a logic board thing? RAM?
Any thoughts, or suggestions for a way to approach further troubleshooting? Thanks!