Customer has a 3252ci that has a F245 error on it. Restarting has not effect on it, but you can remove the ethernet cable and restart it and it works OK as a copier but soon after you reconnect the network cable it comes back with the F245. Thinking that a computer is sending a print job to it that is corrupt. Have asked them to restart their computers this morning and it will be up later to look at it. Am I on the right track? Thanks
-
-
I'd say so, you may be able to see the user name of whoever sent the offending print job in the machine's print log. Could also be a phone sending the print job, seen that a few times too. -
Problem is you cannot see the jobs in the print log, the machine is locked on the error F245 and will not do anything and have to reboot it.Comment
-
Change the IP before you plug the cable in. If its fine after you definitely know you have a corrupt print job on the network. I guess its possible a Phone could still find the device by name or a computer if it was setup that way.
Safer bet is connect your laptop directly to the copier and skip out their network and then print to it.Evil will always triumph because good is dumb.Comment
-
Do what Dark Helmet says. Then run wireshark in the network. I've had a customer that had created a loop on the network flooding it with traffic. This casued the copier to freak out when all that data hit the NIC. At that point, it's not your problem.Comment
-
Definitely a bad print job being sent. I had an HP Print driver make it's own Kyocera driver, and it tried printing, and getting that exact error. Check the print queues on PC's, and assume that even if they said they rebooted, they didn't. I've never had the machine be the cause, it's always a bad print driver/job.Comment
-
Got it working. When I started the machine without the network cable attached it would start up. Plugged my laptop in to the ethernet port and it errored out same as always? That did not make sense at all. So I thought i would hook it up wireless, so I input the settings for the wireless card and it coded out and locked the machine up. Could not get back in to disable the wireless. Had told the shop to bring me a loaner machine and while I was waiting I disconnected the Hard Drive and of course it coded a hard drive error. Plugged it back in and the same F245. I was looking at the board and saw the wireless card and unplugged it and started the machine back up and it worked? Machine started printing documents? Went to computers and printed test pages? So it is working for now? No wireless card but the ethernet works and it is printing again. The wireless card was not even turned on until I turned it on? That did not make any sense?Last edited by kuby; 03-21-2025, 09:16 PM.Comment
-
I have had numerous failures with that Wi-Fi card, but not that. Good job.Comment
-
No that doesn't make sense. I was going to add to make sure IPV6 is disabled, it causes issues like that.Comment
-
Also make sure the firmware is up to date.Comment
-
I don't know if this will help, but when I set up a machine in the shop, be it new or used, I always test the WiFi if it is included with the machine, then turn it off. I do this after updating the firmware.
When installing the machine out in the field I will turn on the WiFi if its required. I have found that just leaving the WiFi on with these devices may cause unforeseen problems. That's why I try very hard to limit the use WiFi. Especially on larger networks. I also find it unfortunate that most ISPs now have the hardwired network separate from the WiFi network. This seems to be the new default.
That's what I do and find I have very few Fxxx problems. And when I do, its much easier to track down.Comment
Comment