<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: tracert but cannot ping host in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881351#M546428</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Based on the information provided there is no way anyone can explain this.&lt;BR /&gt;&lt;BR /&gt;I can try and help with diagnosis:&lt;BR /&gt;1) Check the system nic light and see that the link light is lit.&lt;BR /&gt;2) Check the switch for errors, by looking at it or loggin on.&lt;BR /&gt;3) Check with networking and see if tracert has been diabled. Its pretty common to stop this servivce because it can be used for denial of service.&lt;BR /&gt;4) Check /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Tue, 17 Oct 2006 05:21:21 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-10-17T05:21:21Z</dc:date>
    <item>
      <title>tracert but cannot ping host</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881350#M546427</link>
      <description>I had a case the other day where I could traceroute to a host but could not ping.&lt;BR /&gt;&lt;BR /&gt;And I wondered why?&lt;BR /&gt;&lt;BR /&gt;Can anyone explain?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Oct 2006 05:16:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881350#M546427</guid>
      <dc:creator>SM_3</dc:creator>
      <dc:date>2006-10-17T05:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: tracert but cannot ping host</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881351#M546428</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Based on the information provided there is no way anyone can explain this.&lt;BR /&gt;&lt;BR /&gt;I can try and help with diagnosis:&lt;BR /&gt;1) Check the system nic light and see that the link light is lit.&lt;BR /&gt;2) Check the switch for errors, by looking at it or loggin on.&lt;BR /&gt;3) Check with networking and see if tracert has been diabled. Its pretty common to stop this servivce because it can be used for denial of service.&lt;BR /&gt;4) Check /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 17 Oct 2006 05:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881351#M546428</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-10-17T05:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: tracert but cannot ping host</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881352#M546429</link>
      <description>Hi SM,&lt;BR /&gt;&lt;BR /&gt;ping command sends "ICMP echo request" and receives "ICMP echo reply" these might be blocked.&lt;BR /&gt;&lt;BR /&gt;Traceroute works different:&lt;BR /&gt;It sends some UDP-Packets with a ascending TTL and receives "ICMP time exceeded in-transit" while on the road or &lt;BR /&gt;"ICMP 192.151.52.241 udp port 33440 unreachable".&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;HGH&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Oct 2006 05:38:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881352#M546429</guid>
      <dc:creator>Hemmetter</dc:creator>
      <dc:date>2006-10-17T05:38:14Z</dc:date>
    </item>
    <item>
      <title>Re: tracert but cannot ping host</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881353#M546430</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;According to ping(1M):&lt;BR /&gt;      The ping command sends ICMP Echo Request (ECHO_REQUEST) packets to&lt;BR /&gt;      host once per second.  Each packet that is echoed back via an ICMP&lt;BR /&gt;      Echo Response packet is written to the standard output, including&lt;BR /&gt;      round-trip time.&lt;BR /&gt;&lt;BR /&gt;And according to traceroute(1):&lt;BR /&gt;      This program attempts to trace the route an IPv4/IPv6 packet would&lt;BR /&gt;      follow to some internet host by launching UDP probe packets with a&lt;BR /&gt;      small ttl (time to live) or hop-limit then listening for an ICMPv4 or&lt;BR /&gt;      ICMPv6  "time exceeded" reply from a gateway.  We start our probes&lt;BR /&gt;      with a ttl of one and increase by one until we get an ICMPv4 or ICMPv6&lt;BR /&gt;      "port unreachable" (which means we got to "host") or hit a max (which&lt;BR /&gt;      defaults to 30 hops and can be changed with the -m flag).  Three&lt;BR /&gt;      probes (change with -q flag) are sent at each ttl setting and a line&lt;BR /&gt;      is printed showing the ttl, address of the gateway and round trip time&lt;BR /&gt;      of each probe.  If the probe answers come from different gateways, the&lt;BR /&gt;      address of each responding system will be printed.  If there is no&lt;BR /&gt;      response within a 5 sec. timeout interval (changed with the -w flag),&lt;BR /&gt;      a "*" is printed for that probe.&lt;BR /&gt;&lt;BR /&gt;So, by default, ping sends ICMP packets and traceroute sends UDP packets.  Moreover, the destination ports are different.  A firewall could deny packets based on any of these criteria.&lt;BR /&gt;&lt;BR /&gt;PCS&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Oct 2006 06:22:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracert-but-cannot-ping-host/m-p/3881353#M546430</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-10-17T06:22:44Z</dc:date>
    </item>
  </channel>
</rss>

