Click here to Skip to main content
15,918,303 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
When i applying the filter ip.src == "my ip", almost all of the packets are color-coded "bad checksum". It claims all of the packets' checksums are 0x0000. ATM, I have ~2500 packets in the filter, and probably less than 500 of them aren't highlighted as having a bad checksum. Is this a bug in Wireshark, or is something seriously wrong with my internet connection? Kindly give me your suggestion







Currently i'm using Windows Service in C#.net for communication purpose. If i change my service into Web Service or WCF Service, this packet loss & corruption problem becomes to solution? Kindly give me your guidance
Posted
Updated 15-Nov-11 17:10pm
v4

1 solution

 
Share this answer
 
Comments
Member 7744835 15-Nov-11 4:31am    
I have use that TCP_Checksum_Verification too, but still TCP - "Bad checksum" problem occurring for me.
Mehdi Gholam 15-Nov-11 4:56am    
The doc says that it is "very very rare" that packets are actually corrupted.
Member 7744835 15-Nov-11 5:08am    
Yes, actually my side issue is that, usually the packets transfer properly, at some time, this issues occurring. due to this problem, the packet transfer becomes to block in certain period. At the same, if another user opens our same port and start transfer packets, may be in between it corrupted and lost the communication again.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900