ECOSYS M2635dw - F245 error when starting wireless or ehernet

[kuby]

Have a M2635dw that is giving a F245 error when the wireless or ethernet is started. You can power it up without either option and it will not error out. Hook a ethernet cable to it and 20 seconds later F245. About the same when enabling the wireless after it shows to be running a then about 20 seconds later F245. Anyone ever had this problem?
*******************************************
Printer is now at the shop giving the same error here.

[allstar59]

Check all the computers and dump the print queue. sounds like a workstation is resending a bad print job when the network comes up

[kuby]

Took the printer back to the shop and I get the same results here.

[ihatefinishers13]

Check all the computers and dump the print queue. sounds like a workstation is resending a bad print job when the network comes up

Agreed. Had an HP computer with an HP print driver create it's own Kyocera driver, and the 307ci did NOT like it. Thankfully only 5 PC's I had to sort through, but I initially couldn't find it because the kyocera driver queue was empty. Then went back once I narrowed down that PC and found that driver within the HP Package. Whoever at HP thought that driver was a good idea needs fired. Then again, Kyocera is the worst when it comes to trying to print to one with a different driver, so maybe it's on them, too.

[dalewb74]

i do not share any type of access code. have you tried the typical kyocera 3 digit code that clears so many error messages? the 3 digit code that you use once logged into maintance mode. please don't ask, i will not give it out.

[kuby]

No never heard of that code.

[allstar59]

If it's doing the same thing in the shop then the first thing I'd do is update the firmware.

[tmaged]

I'm currently working on a brand new MA2100CWFX that's doing the same thing. Ours shows F245 in KFS, but the panel shows F000 on the display. It's still in our shop. Ours takes a little while, but only does it with the network cable connected. Haven't tried wireless. All other Kyoceras on our network are fine. I also swithed the IP address to a differnt one to rule out a job coming to that IP address. I've done a wireshark capture and there's an HTTP/XML file that seems to be the trigger, but I'm not positive.

[kuby]

If it's doing the same thing in the shop then the first thing I'd do is update the firmware.

Firmware is up to date, even reflashed it to the full version by USB. No change.

[copykat93]

Following this one... I'm interested in the solution as well.

[ihatefinishers13]

for F24(X), here are the notes from the manual.

(1) Check contact of a DDR memory and perform an operation
check.
(2) Initialize HDD and perform an operation check. (FULL of U024)
* (
3) Carry out U021 Main backup initialization and perform an operation
check.
(4) Exchange a Main board and perform an operation check.
(5) Exchange HDD and perform an operation check. *
(6) Get USBLOG and contact service headquarters.
* Only HDD standard model

[kuby]

OK I think it is fixed. Did a sim u917 and loaded everything on a flash drive, then a u021 initial memory and so far error has not come back. Waiting to see.

Thanks

[tmaged]

U021 seems to have resolved mine as well.

[PrintWhisperer]

I'm currently working on a brand new MA2100CWFX that's doing the same thing. Ours shows F245 in KFS, but the panel shows F000 on the display. It's still in our shop. Ours takes a little while, but only does it with the network cable connected. Haven't tried wireless. All other Kyoceras on our network are fine. I also swithed the IP address to a differnt one to rule out a job coming to that IP address. I've done a wireshark capture and there's an HTTP/XML file that seems to be the trigger, but I'm not positive.

I have seen the HTTP/XML SOAP protocol used as part of WSD discovery (for one) so there may be some broken network exchange stuck in memory.

I know you know the evils of WSD porting, but it seems to be the go-to for the Driver installers so DIY customers seem to often wind up with it in place.

[kuby]

Yes the first thing I check for and if it is using WSD then I change it to use the KX driver. WSD driver is nothing but problems.