[plug] Problem with NE2000 card using thin coax.

[Tom Atkinson]

The cards should autodetect whether to use UTP or coax, but have a look
in the following file for more information on this (i.e whether selection 
can be forced):

/usr/src/linux/drivers/net/ne.c

The other machines will not respond to pings unless they have a routing
table entry for your network.  Do they have this?


On Tue, 2 Mar 1999, David Buddrige wrote:

> Hi all,
> 
> Got a bit of a problem with ne2000 network cards...
> 
> My brother has obtained a number of ne2000 compatible network cards -
> one of which we have put into a 486DX-4-100 which will be a proxy server
> to allow both of my brothers to browse the web simultaenously..
> 
> They have a computer each on their desks (in two different rooms in the
> house) - networked together using thin coax cabling.
> 
> However it seems their prior owners used cat5 twisted pair cable - I've
> got the network card working just fine usnig redhat 5.2 - the machine
> recognises the card - and it can ping itself - but the other two
> machines on the same stretch of coax (maybe 10 meters length in total)
> cannot ping the machine (nor can the linux machine ping it).
> 
> Given that we obtained these cards second hand - we don't have the disks
> to go with them - and in any case we want to configure it under linux
> (the machine is installed with 100% linux - no dos partitions at all).
> Does anyone know how to get the things to use their thin coax port
> rather than the utp port?  (I've actually had the exact problem at my
> own place - I wound up networking the two computer I wanted to connect
> using a twisted-pair cross-over-cable - I've not been able to get the
> cards configured to use the cat5 conenctor to work over thin coax....
> 
> Has anyone seen this before and have a solution? - I've been scanning
> usenet / hotbot, but no luck so far... 8-(
> 
> Thanks heaps in advance... 8-)
> 
> David Buddrige
> buddrige at q-net.net.au
>