ping:send to:no route to host

[KCS_1]

hi~ all.

I running 10.20 on hpux but, have a problem that ping test.

I recieved like that under message when tried to ping to another host(machine1)

#ping 192.XXX.XXX.XXX(machine1)
ping:send to: no route to host
ping:wrote 192.XXX.XXX.XXX 64 chars,ret=-1

my route table on host
[/]# netstat -rn
Routing tables
Dest/Netmask Gateway Flags Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 1459024 lo0 4136
192.xxx.xxx.xxx 192.xxx.xxx.xxx UH 0 9265 lan0 4136
192.xxx.xxx.0 192.xxx.xxx.xxx U 2 0 lan0 1500
default 192.xxx.xxx.254 UG 0 0 lan0 1500
[/]#



question)

what are these mean?

[U.SivaKumar_2]

Hi,
Seems the problem is with your routing table.
If you don't mind give all ip addresses in the
scene.

regards,
U.SivaKumar

[KCS_1]

I modified like this about my question under:

(old part)
#ping 192.XXX.XXX.XXX(machine1) -->

#ping 192.xxx.xxx.3(another host)

[Ravi_8]

Hi,
first you need to check
1. ping loopback (127.0.0.1)
if it's responding check with cable
2.ping your router
if not check with /etc/rc.config.d/netconf file.

this should suffice your need, still doesn't working then you need to check up the lan card.
(lanadmin)

[Sanjay_6]

Hi Patrick,

Is the network configured on this system. Also have you configured the defaule gateway. Can you ping this server ip from another server / workstation.

Try this link from hp cookbook from itrc,

http://us-support2.external.hp.com/iv/data/documents/DE_SW_UX_swrec_EN_01_E/NetConnectivity.pdf

Hope this helps.

regds

[harry d brown jr]

Patrick,

Can you post the ACTUAL results of the "netstat -rnv" without modifying the IP addresses.

It is not a security risk to post IP addresses.

Can you also post the output from "lanscan -v", and "cat /etc/nsswitch.conf"


live free or die
harry

[Christopher Caldwell]

1) ping your loopback
(127.0.0.1)

if that doesn't work, networking is set up correctly.

2) if that does work, ping the IP of the host your on (should be the one maked UH).

if that doesn't work, networking is set up correctly.

3) if that does work, you've probably got an incorrect netmask somewhere in a route.

use
netstat -rnv
to check the actual network address for the route.

If things still seem weird, post the _real_ output of netstat -rnv. The 192 network is RFC 1597 reserved space (we use it too). There should be no security implications when posting that space.

[Christopher Caldwell]

ooops. The post should read "if that doesn't work, networking is _NOT_ set up correctly. Sorry.

[KCS_1]

thanks for all posted all members about the problem.

I tried what ping test for localhost(127.0.0.1)that was got a result good status.
I will try that above suggested the solutions.

anyway, what does these mean under lines about ping test result.
I don't know who anyone can explain to me under situation?

--->

#ping 192.XXX.XXX.XXX
ping:send to: no route to host
ping:wrote 192.XXX.XXX.XXX 64 chars,ret=-1

<---

[Ron Kinner]

I know the U in the netstat output says the lan is up but I'm not sure I believe it especially since the netstat output shows that you have never talked to the default gateway and have only referenced the network route twice and never sent any packets over it.

Let's verify that we have a good network connection before we start to blame the routing.

landadmin
lan
display

should show the status of the network connection. If it's good you should see:

Administration Status (value) = up(1)
Operation Status (value) = up(1)

You might also verify that the speed is the same as your switch or hub thinks it is.

You can also run
lanscan
which should tell you the status but I like lanadmin since I can also check the speed and errors (second page of display) and see if I am getting any packets in or sending any out.

Test the Ethernet connection with

linkloop -n 5 -v macaddress

where macaddress is the mac of another host on the same ethernet hub. This is a hex number so you have to prefix it with 0x and leave off any dots which may have been stuck in it for readability. Since you only have one lan I don't think you need the -i option to tell it which one you want to do it on.

If the network is not up then check the cable, the speed on both end, the switch or hub port, the NIC.

If all of the above is good then check your masks on all machines involved. Can you ping the gateway?

On an aside note: 192.168 is the private address. Any other 192 subnetwork address can be a valid registered internet address. The smart thing to do if you are talking about a real address is to substitute the Network octets with letters:

A.B.C.0 is your network address.
A.B.C.254 would be your router. That way if you are trying to ping A.B.C.1 we know it's on the same subnet whereas A.B.D.1 would not be on the subnet.

Ron

[Steve Labar]

According to your routing table, you don't have a route to get to the 192.x.x network. Your routing table should have at minimum the following entries

Dest Gateway int
127.0.0.1 127.0.0.1 lo0
192.x.x.x 127.0.0.1 lo0 (192.x.x.x should be full ip of stations via local loop address)
192.x.x 192.x.x.x lan0(dest entry should be network address assuming default subnet mask via full ip address of station)

Check your lan0 configuration in /etc/rc.config.d/netconf and try again.

Good Luck.
Steve