[H-GEN] Destination Host Unreachable

Paul Cornford pcornford at optusnet.com.au
Sun Feb 17 21:16:55 EST 2002


[ Humbug *General* list - semi-serious discussions about Humbug and  ]
[ Unix-related topics.  Please observe the list's charter.           ]
[ Worthwhile understanding: http://www.humbug.org.au/netiquette.html ]

Still "Destination Host Unreachable" so no progress here despite 
numerous attempts over the past 10 months (There was no urgency). I 
eventually found that my NIC was faulty (I think) and exchanged it for a 
functional one - and ISA NE2000 compatible. The network consists of my 
own machine (RH 7.2) and a Win2000 laptop which networks fine with 
another Win95 machine. Both cards have tested fine (working well in 
other networks). I have switched cables and the cable I now use is fine 
(also tested on another network). And yes, I have tried the card in 
different slots. The link light is just a steady glow.

Pinging gives me

ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) from 192.168.0.1 : 56(84) bytes of data.
 From 192.168.0.1: Destination Host Unreachable
 From 192.168.0.1: Destination Host Unreachable
 From 192.168.0.1: Destination Host Unreachable

--- 192.168.0.3 ping statistics ---
5 packets transmitted, 0 packets received, +3 errors, 100% packet loss

ifconfig gives me

eth0      Link encap:Ethernet  HWaddr 00:00:B4:82:9F:FC
       inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
       RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       TX packets:0 errors:50 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:100
       RX bytes:0 (0.0 b)  TX bytes:10848 (10.5 Kb)
       Interrupt:9 Base address:0x300

lo        Link encap:Local Loopback
       inet addr:127.0.0.1  Mask:255.0.0.0
       UP LOOPBACK RUNNING  MTU:16436  Metric:1
       RX packets:313 errors:0 dropped:0 overruns:0 frame:0
       TX packets:313 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:0
       RX bytes:22238 (21.7 Kb)  TX bytes:22238 (21.7 Kb)

dmesg gives me

NE*000 ethercard probe at 0x300: 00 00 b4 82 9f fc
eth0: NE2000 found at 0x300, using IRQ 9.

which is correct as I manually set the jumbers on the card (ISA) to 
these values. After attempts at pinging dmesg also gives me

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=119.

I had trouble-free networking up until I upgraded from RH 6.2 to RH 7.0 
10 months ago and I have had no networking since. I have since upgraded 
to RH 7.1 and now RH 7.2. I have exhausted my patience with this thing 
and need help. Any takers?





--
* This is list (humbug) general handled by majordomo at lists.humbug.org.au .
* Postings to this list are only accepted from subscribed addresses of
* lists 'general' or 'general-post'.



More information about the General mailing list