again a ping question

kobem

think due to this sample in the picture






yes another question is on the road , people
when we ping from a host to another (on different network)
if it fails it could be a TCP/IP connection problem and network problem
and then if we put a route for example static route about source and destination we solve
the problem and ping gets succesful.

but the other thing i wondered about ping is pinging the host network address
or pinging to the host's interface ip address ?

which one is true i think we have to ping to the interface of the destination
host not network?[img][/img][img][/img][img][/img][img][/img][img][/img][img][/img][img][/img][img][/img]

kobem

come on , please answer it.

sprkymrk

kobem wrote:

when we ping from a host to another (on different network)
if it fails it could be a TCP/IP connection problem and network problem

Yes, if a ping to a remote destination fails it could be a network problem. It could also be other things such as:
1) The host is down
2) The host does not exist
3) A router or firewall in between is blocking ICMP echoes

kobem wrote:

and then if we put a route for example static route about source and destination we solve
the problem and ping gets succesful.

It's possible, but not likely, that a static route will fix a problem like this, and it definately won't based on your diagram as there is only one way to get from host to host anyway. Unless you have a major misconfiguration issue, the routers are usually always aware of directly attached networks anyway.

kobem wrote:

but the other thing i wondered about ping is pinging the host network address
or pinging to the host's interface ip address ?

which one is true i think we have to ping to the interface of the destination
host not network?

Correct. In all but a few limited circumstances you always ping a host/interface, not a network address. Pinging a network address can be used to cause a denial of service attack, so most systems are hardened against it.