Hi all! I have an Epson 9600 wide format printer, we're experiencing issues where the print job fails, always at the end. I've noticed that every time the job fails, the PC is sending standard ACK packets Output from a successful job: https://www.cloudshark.org/captures/47c1282d852d Output from a failed job: https://www.cloudshark.org/captures/d54ab50636c1 I'm stumped, to be perfectly honest I'm shooting in the dark. Tried LPR vs RAW printing, tried different machines etc, still failing. Any help would be greatly appreciated! edit: bit of extra info, printing from a mac works fine every time. o.O different TCP/IP versions/settings/something? asked 28 Jul '14, 22:37  MikeAnthony edited 31 Jul '14, 00:58 |
One Answer:
A lot of important information is defined at the session start, which we can´t see here. So maybe we need it some day. The main difference between the traces as we can see is the termination of the session. In the successfull trace we can the a normal 4 way session closing (FIN-ACK) In the failure trace we see an anormal session termination indicated by the RST-Bit. In the most cases I analyzed was the root cause a problem above Layer 4. Maybe it is a driver problem at the 192.168.1.91 because this machine sends the RST apparently more or less unmotivated. answered 17 Apr '15, 14:19  Christian_R |
both traces have the same source 192.168.1.91, is it a intermittent issue?
I saw packets going through without issue initially until the source issued RST all of a sudden. Looks like we should understand when and why TCP would send out RST proactively. Weird...
Yep, issue is intermittent. It seems I can completely power cycle the printer (power cord out, turn on to drain residual charge, power back in) and it will successfully print a job (barring issues with the PDF).
Subsequent jobs will then fail until I power cycle the printer again.
First I have a question. Are printing the same job or are they different?
Average RTT time in failed pcap is 2 ms,before sending RST 1.91 waits for almost 20 ms for an ack to come but it didnt receive.so in failure cases you can see that if this pattern is repeating,if yes than there could be some setting on device or system which is causing this.Other thing to find out is why 1.38 didnt sent an ack.