A couple of specific responses below.
At 09:43 PM 4/10/99 -0500, Andrew R. Brink wrote [abridged]:
>> 1. Do you have an IRQ conflict. (This can cause packets to be sent but not
>> received.) Check /proc/interrupts and make sure the NIC is where you think
>> it should be.
>>
>eth0= irq 10, pretty sure nothing else is using 10.
Don't guess; check. What does /proc/interrupts list on IRQ 10 (or has this
changed in the 2.2.x kernel? I'm still running 2.0.something) on each host?
>> 5. After you try to ping, what does /proc/net/arp show about the destination
>> machine? Does its IP address have an associated MAC (Ethernet) address, or
>> is the entry all 0s?
>
>The interesting one,
>IP address HW type Flags HW address Mask
>Device
>192.168.1.2 0x1 0x2 00:20:AE:E0:47:70 *
>eth0
I assume this is on 192.168.1.1 and that 192.168.1.2 similarly reports a MAC
address for 192.168.1.1 . If so, the machines are finding each other, just
not responding to pings afterward.
Which leads to my final thought for now ... might this be a problem peculiar
to ping? That is, can you connect using other services, such as telnet?
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
