Thanks: 
Likes: 
Dislikes: I just got a service call and had this same error in the description. F24B. Also says that pages are coming out painted black which might be a difference between PS and PCL driver. Will be heading out in the morning.
I just got a service call and had this same error in the description. F24B. Also says that pages are coming out painted black which might be a difference between PS and PCL driver. Will be heading out in the morning.
I made the same mistake. Looked very much like a "B". It's not. Corrupt print job. Some times turning off will reset....sometimes not. Turn unit off. If it pops again....power unit off.....unplug network cable.....power up.....if code does not pop......bad print job.......if code pops up again.........wait a minute, I have never seen it come up again with network cable unplugged. Clear print jobs from the cue.
I've had a few that just wouldn't quit sending. If you set your laptop to the printers IP address then connect it in place of the printer, the print job clears. In extreme cases I've had to change the IP of the printer to prevent whatever kind of data from arriving, then one at a time resetting the port on each print driver. =^..^=
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 =^..^=
I had the same issue on a Ecosys P2135DN.
F24B not F248!
I'll go back tomorrow.
I'll try to connect the printer with a LAN cable direct to the computer of the client.
I guess network or main PWB issue....
Grts
Kyocera did some Firmware up-dates on several models to correct these communications errors.
Do a Firmware up-date as a precaution ... what could it hurt ?
"The Serenity Prayer" . . .
God grant me the serenity to accept stupid people , the courage to not waste my time and energy on them , and the wisdom to know that I cannot fix STUPID .
Hello,
machine has latest f/w.
The problem was a driver they used from A Ricoh for a Kyocera printer!
they installed a few weeks ago this kyocera printer (before this ricoh) and used the same ip settings on their print server.
It happend only with one user who send wrong printdata to this Kyocera.
anyway, problem solved!
Grts
Congratulations.Originally Posted by brecht2
On one of my setups, after inputting the new IP address, the machine immediately started spitting out 5 year old emails intended for another printer that had had the same address a long time ago. That should have been a good clue that there were some obsolete print queues that should have been cleared out a long time ago, but weren't. =^..^=
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 =^..^=
Reply With Quote
Bookmarks