Enduser has a Kyocera FS-C2526MFP, called Kyocera and talked with tech support. Tech support said: bad main board. They have a service contract so they call us with "Order us a main board ... ".
I don't know about you, but I don't usually base my actions on a customers diagnosis. It usually does not end up being accurate, and they expect us to eat the part cost when they're wrong, or end up sitting on that part forever. Besides, I have some experience with F248 codes.
The machine is Off upon arrival. I turn it On, and within a few minutes the F248 has popped up. Next I disconnect the network cable and power up: no code. Next I connect my laptop and ping, print, scan, and check the web interface: no code.
The thing I've seen is non-print data being sent to the printer's IP address, especially on large networks. I'm sure there's a way to pin down exactly what sender's IP address, Mac address, and what type of data, but the simplest solution is to change the printer's IP. No need to track down the source if it's sending to an open IP. Plus there are only three endusers in this area. Simplest just to change the port.
You'd think that tech support would have suggested the solution that was the simplest to test, most inexpensive, and needing no parts to fix. You'd think ... but I'll bet they like selling $1000 circuit boards too, necessary or not.
Does anyone have any experience with tracking down the source of this non-print data? I'd imagine Wireshark would be suitable. The problem is, on a really large network a huge amount of data is gathered within a very short period of time. Can you tell Wireshark to watch just one IP address, or a narrow range? And what kind of data can be gathered? Sender IP or Mac address, Date/Time, Port#, Data type? More?
=^..^=
I don't know about you, but I don't usually base my actions on a customers diagnosis. It usually does not end up being accurate, and they expect us to eat the part cost when they're wrong, or end up sitting on that part forever. Besides, I have some experience with F248 codes.
The machine is Off upon arrival. I turn it On, and within a few minutes the F248 has popped up. Next I disconnect the network cable and power up: no code. Next I connect my laptop and ping, print, scan, and check the web interface: no code.
The thing I've seen is non-print data being sent to the printer's IP address, especially on large networks. I'm sure there's a way to pin down exactly what sender's IP address, Mac address, and what type of data, but the simplest solution is to change the printer's IP. No need to track down the source if it's sending to an open IP. Plus there are only three endusers in this area. Simplest just to change the port.
You'd think that tech support would have suggested the solution that was the simplest to test, most inexpensive, and needing no parts to fix. You'd think ... but I'll bet they like selling $1000 circuit boards too, necessary or not.
Does anyone have any experience with tracking down the source of this non-print data? I'd imagine Wireshark would be suitable. The problem is, on a really large network a huge amount of data is gathered within a very short period of time. Can you tell Wireshark to watch just one IP address, or a narrow range? And what kind of data can be gathered? Sender IP or Mac address, Date/Time, Port#, Data type? More?
=^..^=
Comment