How to identify the PING issue

Discussion in 'Cisco' started by bensonlei@yahoo.com.hk, Feb 7, 2011.

  1. Guest

    Hi,

    According to Cisco Document :
    http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1907.html

    Three issues for ping :

    "." --- Each period indicates that the network server timed out while
    waiting for a reply.
    This message can indicate many problems:
    • ping was blocked by an access list or firewall.
    • A router along the path did not have a route to the
    destination and did not send an ICMP destination
    unreachable message.
    • A physical connectivity problem occurred somewhere
    along the path.

    --------------------------------------------------------

    We identified:
    1. Router path is learned and correct.
    2. Physical connectivity is correct
    3. We do not add any ACL in the Router

    Question:
    How can we identify it is a IOS issue ?

    Cheers
     
    , Feb 7, 2011
    #1
    1. Advertising

  2. Hello,

    I am not a true expert, but first question when resolving ping issues is
    for me: are the subnet masks and default gateways on all devices along
    the ping path (especially on the ping target) configured correctly?

    I would copy the network scenario into packet tracer or another
    IOS-Simulation/Emulation-Software (GNS3 is an example) and debug there.
    Packet tracer makes such problems really visible, although many
    IOS-features like bridging/ip-accesslists on bridges and many more are
    not implemented. DHCP might help to prevent such problems in the future...

    just a thought...


    Am 07.02.2011 08:38, schrieb :
    > Hi,
    >
    > According to Cisco Document :
    > http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1907.html
    >
    > Three issues for ping :
    >
    > "." --- Each period indicates that the network server timed out while
    > waiting for a reply.
    > This message can indicate many problems:
    > • ping was blocked by an access list or firewall.
    > • A router along the path did not have a route to the
    > destination and did not send an ICMP destination
    > unreachable message.
    > • A physical connectivity problem occurred somewhere
    > along the path.
    >
    > --------------------------------------------------------
    >
    > We identified:
    > 1. Router path is learned and correct.
    > 2. Physical connectivity is correct
    > 3. We do not add any ACL in the Router
    >
    > Question:
    > How can we identify it is a IOS issue ?
    >
    > Cheers
    >
    >
     
    Thomas Caspari, Feb 8, 2011
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. =?Utf-8?B?V0pQQw==?=

    Can not ping myself, but can ping others

    =?Utf-8?B?V0pQQw==?=, Dec 25, 2004, in forum: Wireless Networking
    Replies:
    6
    Views:
    6,018
    Chuck
    Dec 26, 2004
  2. Bob Simon
    Replies:
    8
    Views:
    7,205
    John Lamar
    Jan 19, 2005
  3. gruffydd

    ping ping Why

    gruffydd, Dec 28, 2004, in forum: Computer Support
    Replies:
    3
    Views:
    568
    gruffydd
    Dec 29, 2004
  4. Replies:
    2
    Views:
    635
    =?Utf-8?B?SmFmZnNlcg==?=
    Aug 3, 2006
  5. Replies:
    0
    Views:
    525
Loading...

Share This Page