Destination host unreachable

jitendra bhaskar · 04-24-2010, 07:15 AM

i have 2 box

in one box i have win-xp and redhat-9 (New Mother board)
other box have only redhat-9 (old Intel 810-e Mother board)

on new box (Win-XP and Redhat) have onboard LAN card which is not recognize by linux so i put external LAN card with same. i disable onboard LAN

IP 192.168.0.10
Net mast 255.255.255.0
gateway 192.168.0.254
primary name server 192.168.0.1

On old box (Redhat) have external LAN card.

IP 192.168.0.20
Net mast 255.255.255.0
gateway 192.168.0.254
primary name server 192.168.0.1

when i ping win to linux and linux to win its pinging and i can use samba on windows

But i cant ping new box linux to old box linux or vise versa
getting Destination host unreachable

if i ping from new to old box and use #tcpdump on old machine then it give o/p

when i ping from old to new and use #tcpdump on new it wont give o/p

so i cant use NFS/NIS due to this

i dont understand where data getting block
if its working on widows to linux means there is no issue with my hardware.

so please help me to solve this issue.

dogstar1 · 05-03-2010, 08:10 PM

Box 1 = IP 192.168.0.10 Win/Linux (which one? or both in virtual? If so what is the 3rd IP or is it using NAT?)
Box 2 = IP 192.168.0.20 Linux

.........SMB.........
.Box 1 ---> Box 2.
..Win.........Linux..

.........ICMP........
.Box 1 -/-> Box 2.
.Linux........Linux..

Box 1
Can you ping 192.168.0.254?
Check 'iptables -L' for firewall issues.

Box 2
Is NFS running?
Are FW rules correct?

LVsFINEST · 05-03-2010, 09:08 PM

Right off the top of my head I'd say IPtables on your new linux box is the problem. By default, RHEL versions do not just drop packets silently, IPtables issues an icmp destination unreachable if packets do not match any rules. With that said, it sounds like your running VMs (Windows and Linux on one box?) and the issue may also lie in the network configuration of your VM host. Can either of the machines reach the Internet?

To quickly verify if IPtables is the culprit, you could do:

'/sbin/service iptables stop'

and re-test.

Posting the output of '/sbin/iptables -L' will help too.

SuperJediWombat! · 05-03-2010, 09:22 PM

post the output of:

Code:

ifconfig
ip route
iptables-save

I suspect that it's just your IP (mis)configuration.