I have a remote LAN with multiple printers and some of these devices are taking a long time to spool and complete a print job (one in particular upwards of 10 minutes). I have taken captures from a Windows client on site to 4 different printers, but I can't really see anything different in any of the 4 captures. Can someone advise what I should be looking for based on the symptoms? Also, I've noticed that a few people use Cloudshark to upload captures to a central repository. Does anyone have any suggestions on a free repository or sharing solution? asked 21 Aug '13, 09:56  mkeith25 |
One Answer:
If it is just some printers in the same remote location, I'd start at comparing the syn_ack packets: tcp window size, window_scaling, offered mss option. Also, monitor the bytes_in_flight and see if this saturates the pipe. Look at the delta_time between packets and see whether you wait for an ack, opening the window again. tcp.analysis.flags should give you additional suspects ... answered 21 Aug '13, 11:23  mrEEde2 |
The special thing about Cloudshark is that it can interpret the capture file in the same manner as Wireshark so collaborators don't need to have their own copy of Wireshark.
For generally capture file sharing any shared file storage would do, e.g. Google Drive, SkyDrive, Dropbox etc.