Is he using a crossover cable instead of a hub? I don't have the original
posts as I get my e's from about 5 different locations thru the day.
If this is so, is he sure the cable is good? Is this the actual same cable
that he used while the pc's were running windows? ....or in other words was
he running them as windows in the same environment?
He has triple checked that he has unique id's on each pc? If so, I would
ditch those addresses and try 2 others.
Are these PCI nics or ISA nics. I have had mucho trouble with PCI nics on
some motherboards using IP, and go to ISA and have no problem.
Connie
>eric - i'll take your word for it that both pc's talk to each other in
windows
>(vi IP and NOT NETBUI) - so it's not a wiring problem - buy a mini hub huh?
>that way u can see the link status lights :)
>
>ps: - ray - how do i compile kpilot (palmpilot s/w runs for kde) so i can
>get it to run under xfce?? - thing won't compile - it's complaining about
>QT and stuff.
>
>
>the rude
>_______________________________________________________________________
>
>
>Ray Olszewski wrote:
>
>> Eric --
>>
>> I'm basically stumped. Everything you posted looks right to me. So we're
>> down to longshots.
>>
>> 1. Are the IP addresses the Linux hosts use the exact same ones they use
>> when booted in Windows? If not, make them match and see if that helps.
>>
>> 2. When both are in Linux mode, you've said the A cannot ping B. Can B
ping
>> A? If it can, A probably has some sort of problem with its broadcast
>> address, such that ARP requests aren't being processed properly.
>>
>> 3. After you try to ping to B from A, what does A's ARP table look like
>> (it's in /proc/net/arp on my hosts, probably on yours too)? How about
B's? A
>> to B, same questions.
>>
>> 4. Does A have ANY PnP hardware in it? Like a Winmodem, perhaps?
Something
>> that might be interfering with reception on IRQ 10? (I've seen this
happen
>> to NICs that were set for IRQ 3
>>
>> -- they show okay in /proc/interrupts,
>> but a
>>
>> Winmodem on IRQ 3 still picks off only incoming packets. For
>> it to happen
>>
>> on IRQ 10 would be unusual, but not impossible.)
>>
>> 5. Even though the nay-saying responses were right, I'd try using
different
>> IP addresses, ones that don't include 0s. The standards say that 0s are
okay
>> eveywhere except at the end (10.0.0.0 would not be valid, for example,
but
>> only because the rightmost 0 makes it a network address), but software
has
>> been known not to implement the standards correctly. I'd be surprised if
>> Linux netowrking got this wrong -- if it had, everyone would know about
it,
>> especially in a popular release like RH 5.2 (and I know from my own
>> experience that this is NOT a problem with SLackware). But, as I said,
we're
>> down to long shots.
>>
>> At 11:57 AM 7/21/99 -0400, Eric P. wrote:
>> >Hi,
>> >I did the ifconfig and route -n. and her are the results
>> >for each computer.
>>
>> [rest deleted]
>>
>> ------------------------------------"Never tell me the odds!"---
>> Ray Olszewski -- Han Solo
>> Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
>> ----------------------------------------------------------------
