Re: After restarting Destination host unreachable
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Tue, 09 Jan 2007 21:04:06 -0600
On 9 Jan 2007, in the Usenet newsgroup linux.redhat, in article
<1168346277.794184.190560@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, pandi wrote:
I have two network cards. One card is connected is LAN. Another one
is connected to internet switch.
Verbal descriptions loose a lot - what exactly does the routing table
look like '/sbin/route -n'
Ip: 132.149.2.75
mask:255.255.255.0
gateway: 132.149.2.254
Be careful. Where does 132.149.2.254 lead to?
Ip:192.168.12.50
mask:255.255.255.0
gateway: 192.168.12.1
And the same question here. Where does 192.168.12.1 lead to?
A very common problem thanks to microsoft mis-information is that people
mis-understand what a gateway means. In Linux, it means a gateway to
another network that is NOT attached to this computer. The "default"
gateway means the gateway to the world, and unless you are using advanced
routing techniques, there can be only one listed in your routing table.
Upto yesterday I can able to ping my locay gateway ( 132.149.2.254).
and I can able to ping the internet Internet dns through gateway
(192.168.12.1->routerip>dns)..
so Obivously i can able to access the internet .
Well, it's not obvious to everyone. 132.149.2.254 belongs to CNES in
France, and you are posting from Tamil Nadu State - a quarter of the
way around the world.
Everything was working fine, till I restart the server today . After
restarting I cannot access the internet.
And what did you change? Since the PREVIOUS time you restarted?
132.149.2.75 (132.149.2.75) 2994.793 ms !H 2998.691 ms !H 3000.332 !H
You'll have to use a packet sniffer, but some host (possibly your own
computer) is telling you that it can't talk to that host, OR the router
that you can talk to knows the host doesn't exist.
192.168.12.50 (192.168.12.50) 2974.793 ms !H 3998.691 ms !H 3800.332
Same answer
I have checked the cables, links, and gateway and routes. everything is
okay..
Well, obviously something isn't as well as you think. Look at the
routing table (/sbin/route -n) and the individual NIC (/sbin/ifconfig -a)
paying particular attention to the errors reported. Look also at the
boot messages.
Using mii-tool i checked the link. Everythiong is okay.
Then why doesn't your networking work?
I am using Fedora core 5. First i did all these things in fedora...
After I think it might be a software corruption,
So now I installed Redhat linux 9.
But still I am getting the same error messages
Sounds more like a PBCAK. (operator error).
What I have to do ?
/sbin/route -n ; /sbin/ifconfig -a
Old guy
.
- References:
- After restarting Destination host unreachable
- From: pandi
- After restarting Destination host unreachable
- Prev by Date: Re: Daylight Saving Time patches for RH 7.1/7.3
- Next by Date: Re: HP server, Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet, eth1 cant get 1000bps
- Previous by thread: After restarting Destination host unreachable
- Next by thread: Re: After restarting Destination host unreachable
- Index(es):
Relevant Pages
|