Il 15/07/2012 09:14, James Howard Young ha scritto:
I think that the delay you see between packets 716 and 718 is simply
the host processing time it took host 192.168.1.12 (the machine that
the sniffer was running on) to generate the HTTP POST packet sent
in packet 718.
Hope this helps,
Thanks all guys for good answers, so I see that STP is not the problem
in my case and these delay second due to host processing time (client).
But I don't know why this application take too many time to start (about
25 seconds), please take a look on this second trace (another cusotmer
LAN with the same app starts):
http://www.cloudshark.org/captures/e95c1068086f
from packets 680 to 701 has been nearly 2 seconds meanwhile there are
many multicast packets, can this a contribute to cause this delay?
And in the same case (and same trace file but beacuse is too big I've
split the file), I've seen many TDS protocol (SQL transaction) with
malformed packets:
http://www.cloudshark.org/captures/2c90ee59e7fa
take a look at packets 80 , 156, 213, 245, 251, 275, 297, 307 , etc..
what do you think of this?
Andrew