[H-GEN] Destination Host Unreachable
ben.carlyle at invensys.com
ben.carlyle at invensys.com
Mon Feb 18 00:05:38 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 ]
Paul,
While the "Destination Host Unreachable" message could be a routing issue,
it is just as likely to be an ARP issue. If nothing's going down the
wire, then ARP messages can't get around the network so hosts with correct
routing data still can't be mapped from IP addresses to ethernet MAC
addresses.
Now onto the Tx timeout. I used to get this on my NE2000 compatable when
the cable wasn't plugged in. This only applied to the coax connector when
it hadn't decided to change over to the 10base2 yet, which thankfully it
did automatically. Many cards of the period did not change over
automatically, and once reset required a dos program to fiddle a bit in
the card to point it to the right interface. Does your card have 10base2
and 10baseT connections? This problem may be as simple as the card looking
at the wrong one...
:)
Benjamin.
Paul Cornford <pcornford at optusnet.com.au>
Sent by: Majordomo <majordom at caliburn.humbug.org.au>
18/02/02 12:16
Please respond to general
To: Humbug <general at lists.humbug.org.au>
cc:
Subject: [H-GEN] Destination Host Unreachable
[ 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'.
--
* 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