Re: Can't ping RH host - resend#2

[Kevin Colby <kevinc grainsystems com>]

V. Leveque wrote:
> 
> Answers:
> 
> 1. Yes -- a Laser printer, Appletalk bridge, BSD box, NT box,
> & Linux box.  I pulled everything except the Linux and NT box
> - no ping.  I even connected the 2 with crossover cable,
> bypassing the hub - no ping.

So the Linux box can't ping anything on the network,
but the NT box can ping everything except the Linux box, right?

> 2. NICS for both are 3com 509B.  I've swapped the NICs.
> Both NICs work in the NT box.

Hrm.  As others mentioned, try swapping all cables as well.

> As a long shot, would the definition of the gateway, name server,
> or domain affect any of this?  I assume on a local net with no
> routers or gateway that these values do not matter.  True?

Default routes and such shouldn't really matter at the subnet
level, but you check your routing table out anyway.
I can't imagine that it would be wrong, but post it here if
you can.  You should have a network route (probably ends in 0)
for your local subnet that says eth0.  You shouldn't even have
a default route or really any others except for a loopback.

> Is there a NIC self diagnostic I can do in Linux?

Well, if ifconfig is happy, then generally your driver is
working correctly.  The only exception to this that I have
seen are 10/100 negotiation problems.  The 905b's in
particular used to have a driver that had trouble with 100Mb.
It would auto-sense 100 and then just stop working.  Plug
it in to a 10Mb hub and viola!  These kind of problems
should be more or less fixed by now though, and I believe
RH 6.0 had no trouble with that card (at 100Mb/s).

	- Kevin Colby
	  kevinc grainsystems com