Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

network unreachable

Status
Not open for further replies.

gosuc

Technical User
Mar 12, 2001
36
DE
Hi fellowadmins,

My Hp-Box is running HP-UX10.20, and I have some routing-
problem.
The HP-Box belongs to network 196.1.1.0, and the
default-router is 196.1.1.99. When i wnat to ping a
system in network 192.168.2.0 (via default router),
I get no response. I tried to manually create a route
with route add net 192.168.2.0 netmask 255.255.255.0
196.1.1.99, the response of which was
"add net 192.168.2.0: gateway 196.1.1.99."
The ping from the HP-Box to a system in the 192-net was
not sucessful (no response).
When I tried an arp -a|grep 192 I received:
?(192.168.2.10)at (incomplete).
The funny thing is, that all other systems from network
196 can reach all systems in network 192 and vice versa.
The HP-Box can only reach the systems on its own network.
The ping from the HP-Box to the default router works fine.

Does anyone hav an idea what the cause may be? Any help
is very welcome.

Regards,
Gottfried

 
Run a traceroute to the destination and see how far it gets. Also, this will ensure that the request is going out on the default router. Please post your route table and network card information.

# traceroute 192.168.2.10

# netstat -rn
# ifconfig lan0

crowe
 
traceroute showed:

1 * * * *
2 * * * *
3 * * * *
and so on, until I interrupted it with Ctrl C.

I will have to do ifconfig and netstat tomorrow, as I am
not in the office anymore. But I recall, that with
netstat -nr there was no 192-address. But I remember,
I have only seen U and UH designations for the systems, but
not G (for Gateway). But I will look up the details tomorrow.
 
If you don't have G then add that
#> route add default ip 1

Sachin
 
SMMARY: Network unreachable

Hi fellow-admins,

after being back from vacation, I'd like to tell you the
solution:

The route add command was not accepted before I deleted
the route first. After deleting and re-adding the route,
the problem was solved. One question still remains - Why
didn't the system tell me, there is an 'old' route-info
about the same route available (although not working).

Thanks for all who responded.

Regards
Gottfried
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top