- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2019 05:30 AM
Hi,
Im checking a infrastructure using ping command. Ping it doesn't work but yes simulation part. What is correct result and why happen this?
Thanks in advance
Solved! Go to Solution.
- Labels:
-
Other Routers
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2019 06:04 AM
Hi @sir_ulrick
I see you are using PacketTracer.
When using the simulated ping it is not necessary to which interface of the indicated device you are pointing.
A ping made on the cmd of the PC is more accurate.
In addition, you should keep in mind that PT does not always behave as it should.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2019 07:09 AM
Hi,
As you are getting Destination Host Unreachable on the screen means source (from where Ping is started) getting reply packet with some error.
There is a small difference between destination host unreachable and request timed out as
Destination Host Unreachable
This message indicates one of two problems: either the local system has no route to the desired destination or a remote router reports that it has no route to the destination. If the message is simply "Destination Host Unreachable," then there is no route from the local system, and the packets to be sent were never put on the wire. If the message is "Reply From < IP address >: Destination Host Unreachable," then the routing problem occurred at a remote router, whose address is indicated by the "< IP address >" field. This also may that some devices as FortiGate or Sophos firewall having "Deny" and "Reject" option to block the traffic so it may that destination itself configured with "Reject" option.
Request Timed Out
This message indicates that no Echo Reply messages were received within the default time of 1 second. This can be due to many different causes; the most common include network congestion, failure of the ARP request, packet filtering, routing error, or a silent discard.
Due to this difference, you are getting reply packet from any node on the way of the destination node.
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2019 06:04 AM
Hi @sir_ulrick
I see you are using PacketTracer.
When using the simulated ping it is not necessary to which interface of the indicated device you are pointing.
A ping made on the cmd of the PC is more accurate.
In addition, you should keep in mind that PT does not always behave as it should.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2019 07:09 AM
Hi,
As you are getting Destination Host Unreachable on the screen means source (from where Ping is started) getting reply packet with some error.
There is a small difference between destination host unreachable and request timed out as
Destination Host Unreachable
This message indicates one of two problems: either the local system has no route to the desired destination or a remote router reports that it has no route to the destination. If the message is simply "Destination Host Unreachable," then there is no route from the local system, and the packets to be sent were never put on the wire. If the message is "Reply From < IP address >: Destination Host Unreachable," then the routing problem occurred at a remote router, whose address is indicated by the "< IP address >" field. This also may that some devices as FortiGate or Sophos firewall having "Deny" and "Reject" option to block the traffic so it may that destination itself configured with "Reject" option.
Request Timed Out
This message indicates that no Echo Reply messages were received within the default time of 1 second. This can be due to many different causes; the most common include network congestion, failure of the ARP request, packet filtering, routing error, or a silent discard.
Due to this difference, you are getting reply packet from any node on the way of the destination node.
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!
