CMD Ping MISCOMPARE at offset 3

[sle3pingz]

Hello, i want ask about CMD when Pinging, Today i see something weird with my Ping ...

here's the Result :

Reply from [URL="http://175.103.60.55"]175.103.60.55[/URL]: bytes=32 time=355ms TTL=53
Reply from [URL="http://175.103.60.55"]175.103.60.55[/URL]: bytes=32 time=253ms TTL=53
Reply from [URL="http://175.103.60.55"]175.103.60.55[/URL]: bytes=32 time=136ms TTL=53
Reply from [URL="http://175.103.60.55"]175.103.60.55[/URL]: bytes=32 - MISCOMPARE at offset 3 - time=138ms TTL=53
Reply from [URL="http://175.103.60.55"]175.103.60.55[/URL]: bytes=32 time=134ms TTL=53

i want ask , what was that - MISCOMPARE at offset 3 - ?
sorry for asking weird Question, and Thanks ...

 

[Alejandro85]

It happens when the ping was answered, but the return packets don't match what was sent exactly. Sure it's weird, but I would not be worried if it happens only once, but if it's frequent it may signal a problem.

The official explanation is this:
Error Message:

 

[sle3pingz]

Thanks ale, did you mean maybe they server fault? not my Hardware / Modem wrong, right?

 

[sle3pingz]

It happens when the ping was answered, but the return packets don't match what was sent exactly. Sure it's weird, but I would not be worried if it happens only once, but if it's frequent it may signal a problem.

The official explanation is this:
Error Message:

you mean Signal problem? i using External Modem, is that you mean my Modem Signal Connection have a problem ?

 

[Alejandro85]

That means that there was a fault "somewhere" in the route, but it's difficult to tell where. Maybe it's your computer, network card, ISP, internet connection across the world, or the server itself, there are really many factors that can go wrong. And even then, maybe it was just a temporary problem already fixed.

If you got the error just once, I would not worry about it, probably a one-time glitch in the infrastructure between the server and you. But if you keep getting that message, sure there is something wrong. To check, maybe you can ping something else, a completely different server just to see if the problem is on your side or on theirs.

 

[sle3pingz]

That means that there was a fault "somewhere" in the route, but it's difficult to tell where. Maybe it's your computer, network card, ISP, internet connection across the world, or the server itself, there are really many factors that can go wrong. And even then, maybe it was just a temporary problem already fixed.

If you got the error just once, I would not worry about it, probably a one-time glitch in the infrastructure between the server and you. But if you keep getting that message, sure there is something wrong. To check, maybe you can ping something else, a completely different server just to see if the problem is on your side or on theirs.

it's sometimes glitch like this, i don't know what's the problem , i didn't do anything, this happened two or three days ago, ...

Reply from 202.3.208.138: bytes=32 time=96ms TTL=56
Reply from 202.3.208.138: bytes=32 time=86ms TTL=56
Reply from 202.3.208.138: bytes=32 time=86ms TTL=56
Reply from 202.3.208.138: bytes=32 time=176ms TTL=56
Reply from 202.3.208.138: bytes=32 - MISCOMPARE at offset 3 - time=126ms TTL=56
Reply from 202.3.208.138: bytes=32 time=86ms TTL=56
Reply from 202.3.208.138: bytes=32 time=86ms TTL=56
Reply from 202.3.208.138: bytes=32 time=86ms TTL=56
Reply from 202.3.208.138: bytes=32 time=86ms TTL=56
Reply from 202.3.208.138: bytes=32 time=1437ms TTL=56
Reply from 202.3.208.138: bytes=32 time=378ms TTL=56
Reply from 202.3.208.138: bytes=32 time=327ms TTL=56
Reply from 202.3.208.138: bytes=32 time=767ms TTL=56