Hello Sameer.
Looking over the cloudshark capture, it simply looks like the UDP port 33437 at the destination device of 192.168.3.1 is just not listening. You get a Type 3 Code 3 result which means, according to RFC 792, that the UDP port is blocked, possibly by a firewall.
This drop of the packet is different than the drop of the packet that occurs due to TTL going to 0. In such a case, you have different Type and Code numbers such as is the case when the TTL became 0 when the device 192.168.23.3 was reached in the previous packet:
In any case, the reason why this error is generated is because the port is blocked. The device has been reached successfully, since it is responding, but the specific port is unavailable and thus the response is an error message and not an echo reply.
I hope this has been helpful!
Laz