<?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: Rare IP from ping in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105615#M83254</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;   First u try to get traceroute of the packet.Otherwise the Hostname to ipaddress naming may not be updated in the server and client side..&lt;BR /&gt;   &lt;BR /&gt;Regds&lt;BR /&gt;Palani&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Dec 2007 03:47:21 GMT</pubDate>
    <dc:creator>palaniappan.sp</dc:creator>
    <dc:date>2007-12-05T03:47:21Z</dc:date>
    <item>
      <title>Rare IP from ping</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105611#M83250</link>
      <description>Red Hat Enterprise Linux.&lt;BR /&gt;&lt;BR /&gt;I rebooted a server and put a "ping -t" to work to know when it is available again.&lt;BR /&gt;&lt;BR /&gt;But, once the server is not responding (because it is rebooting) the IP responding change:&lt;BR /&gt;&lt;BR /&gt;C:\&amp;gt;ping dev -t&lt;BR /&gt;&lt;BR /&gt;Pinging dev.lc.org [172.16.18.59] with 32 bytes of data:&lt;BR /&gt;&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;Reply from 201.161.22.122: Destination host unreachable.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;1) Why?&lt;BR /&gt;2) What does it means?</description>
      <pubDate>Tue, 20 Nov 2007 12:06:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105611#M83250</guid>
      <dc:creator>Tonatiuh</dc:creator>
      <dc:date>2007-11-20T12:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: Rare IP from ping</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105612#M83251</link>
      <description>Try the "traceroute" command to see where the network packets "hop" on their way to their destination [172.16.18.59]]. You may well get the answer. :)</description>
      <pubDate>Tue, 20 Nov 2007 12:47:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105612#M83251</guid>
      <dc:creator>~sesh</dc:creator>
      <dc:date>2007-11-20T12:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: Rare IP from ping</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105613#M83252</link>
      <description>Probably, 201.161.22.122 is the gateway that allows you to reach the remote host, and is reporting that the host is unreachable.&lt;BR /&gt;&lt;BR /&gt;Check your network route table with:&lt;BR /&gt;&lt;BR /&gt;netstat -nr&lt;BR /&gt;&lt;BR /&gt;You should see and entry for 201.161.22.122.</description>
      <pubDate>Tue, 20 Nov 2007 12:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105613#M83252</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-11-20T12:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: Rare IP from ping</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105614#M83253</link>
      <description>check if you have any routing set like one below&lt;BR /&gt;&lt;BR /&gt;0.0.0.0         201.161.22.122 0.0.0.0         UG        0 0          0 ethx&lt;BR /&gt;&lt;BR /&gt;or add one &lt;BR /&gt;&lt;BR /&gt;#route add default 201.161.22.122&lt;BR /&gt;&lt;BR /&gt;or something similar &lt;BR /&gt;&lt;BR /&gt;#route add -net 172.16.18.0 netmask 255.255.255.0 gw 201.161.22.122</description>
      <pubDate>Tue, 20 Nov 2007 20:39:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105614#M83253</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-11-20T20:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: Rare IP from ping</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105615#M83254</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;   First u try to get traceroute of the packet.Otherwise the Hostname to ipaddress naming may not be updated in the server and client side..&lt;BR /&gt;   &lt;BR /&gt;Regds&lt;BR /&gt;Palani&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Dec 2007 03:47:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rare-ip-from-ping/m-p/4105615#M83254</guid>
      <dc:creator>palaniappan.sp</dc:creator>
      <dc:date>2007-12-05T03:47:21Z</dc:date>
    </item>
  </channel>
</rss>

