You say you set up the Linux NIC "best I can". To spot the problem, we'll
need a bit more detail than that.
1. On the Linux host, can you successfully "telnet localhost"? This doesn't
test the NIC (Network Interface Card), but it does verify that other pieces
of the system are set up correctly for network access.
2. What is the output of "ifconfig eth0"? It should identify the NIC by its
MAC number (an Ethernet address), plus list the IP address, netmask, etc.,
for the card. If it doesn't do all of this, you left something out in your
setup.
3. If you run "more /proc/interrupts", do you see the Ethernet card listed?
(I don't know what this will look like exactly; it should display the name
of the card, and you don't say what card it is.) If not, the kernel didn't
find the card when it booted -- either you don't have support for the card
installed, or you have the card on an interrupt that is already used by
something else (IRQ 3 is typical if you're having this particular problem).
You can also use "dmesg" to review the boottime messages from the kernel to
see if it finds the NIC.
4. When testing conectivity, how are you physically connecting the two
machines? You have to do it through a hub, or use a special "cross-connect"
cable. You can't just connect them with an ordinary Ethernet cable. (Your
comment about the card lights came through incomplete, BTW.)
I'm not an expert on Windows, but your setup there sounds okay -- if not
ideal, at least good enough for a test. I assume you have been trying to
telnet by IP number, not hostname ... if not, try it that way.
At 04:50 PM 5/22/99 +0100, Ailwyn Burgess wrote [in part]:
>I have installed my network card into my linux box (RH5.2) and set it up
>(best I can).
>
>I know that the network card in my laptop is ok because it will connect to
>an NT network, but I can't telnet between the two machines (and the lights
>on the cards which show
>
>Is there any way of running a "self test" on the network card from linux?
>
>What clients/protocols/tcp settings do I need in Win95 to make the
>connection - I'm currently using client for microsoft networks/tcp>ethernet
>binding wins is disabled dns is disabled and an ip of 192.192.192.2
>(192.192.192.1 on the linux box) and a 255.255.255.0 netmask
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
