Very Computer

by **Jan Walte** » Sat, 23 Aug 1997 04:00:00

Hi everyone,

I put a second NE2000 card into one of my Linux boxes and discovered
some interesting behaviour.

The first card is a PCI RTL8029 chipset-based card, and the second card
is an ISA RTL8019 based card.

Here is what happens:

1. Card 1 (eth0, the PCI one) operates normally, on a RG-58 Thinnet coax
medium.
2. Card 2 refuses to send packets successfully over CAT5 wire. The Link
lite is active on both the card and the concentrator, so the cable is
fine.
3. When connected to a separate coax segment, the second card works
fine. Yes, I checked the card configuration, and it's set to the right
cable type each time, and I also tried auto-detect.
4. Card 1 connected to the Cat5 wire has the same problem - it works on
coax, and does not otherwise.
5. ifconfig shows that the card is receiving packets, even when
connected to the cat5 wire. The lights blink too...
6. a traceroute -n to a host on the network spits back the IP number of
the card (correct) and then a !H, meaning host is not there or
unreachable when connected to cat5.

I played with various configurations and all that, to no avail. The
machine does not have another OS on it, but the link diagnostics on the
ethernet driver disks show that the card does receive frames from other
cards.

What did I miss here?

Any suggestions appreciated.

Cheers,

Jan
--
---
facts below, opinion above
// Centurion Services
// Quality from the Start
// Fax: (604) 279-1800

// www.ipipeline.net/centurion
// *** now hiring: www.ipipeline.net/centurion/jobs

by **Tom Yor** » Wed, 27 Aug 1997 04:00:00

1. Check cabling. Your link LED is simply a link LED, not an error
detection
LED. It could be that one of the two wires for the transmit or receive
pair are
bad.

Are you plugging the TP connection into a hub? Direct connection will not
work unless you have a crossover cable.

Hope this helps,
Tom

by **Jan Walte** » Fri, 29 Aug 1997 04:00:00

> Hi everyone,

> I put a second NE2000 card into one of my Linux boxes and discovered
> some interesting behaviour.

This problem turned out not be a Linux or network card problem at all -
the problem was with the cable modem. Apparently the cable modems my
provider uses read the ethernet card address of the adapter on the other
end and somehow require it to work. Since one box (the first one hooked
into the modem) worked, it was using that ethernet address. I restarted
the modem, and voila, it's up. It would have been nice for front level
tech support to know about that though...

Thanks to everyone for their hellp and input.

Jan Walter
---
facts below, opinion above
// Centurion Services
// Quality from the Start
// Fax: (604) 279-1800

// www.ipipeline.net/centurion
// *** now hiring: www.ipipeline.net/centurion/jobs

Very Computer

Really weird NE2000 problem

Really weird NE2000 problem

Really weird NE2000 problem

Really weird NE2000 problem