Hi again.
Hetz told me to try 192.168.1.x instead of 192.168.0.x, and it still
doesn't work.
I also have found something suspicious in the behavior of the RH5.2
computer (192.168.0.2). (also when it's 192.168.1.2)
When I use the RH6 computer (.1) to ping the (.2) computer, both of the
lights blink,
meaning that the RH5.2 gets the ping but doesn't respond to it. (maybe
it's thinking it's not .2 for some reason),
also meaning that the cable is fine.
BUT - when I use .2 to ping .1 the lights blink once and then stop,
meaning it doesn't even try to send anything. (not more than once
anyway).
Moreover, the lights blink when I send to 192.168.0.255 and 192.168.0.0
from both computers (and it reports the ping to be successful).
comparing the output of ifconfig and route -n everything is the same
except the machines IP.
This is wierd. (I'll update if I'll find more details)
Please help,
Thanks,
Yoni.
BTW,
Both kernels are the ones I got with redhat originally,
(the new one i used with rh5.2 was compiled without ethernet support, so
i just switched to the old one)
So I don't think there's a problem with the kernel.
Yoni Elhanani wrote:
>
> Hello.
>
> I have tried to config a network on my two computers this afternoon,
> (I have 2 computers now, none was ever networked but ppp)
> One of them runs RefHat 5.2 and the other RedHat 6.0
>
> The cards are ISA PnP NE2000,
> which I configured with isapnp, and it works.
> (it blinks when I try to use it)
>
> After I ran linuxconf/netconf/netcfg (and changed /etc/hosts so I can
> type a name instead of an address),
> When I rebooted it connected me to the network. (192.168.0.1 and
> 192.168.0.2)
> (though RH6 had problems with isapnp on booting my RH6, I used it
> manualy in the end).
> I tried to ping from every computer to itself (not via localhost, but
> via the network addresses) and it worked fine.
> But when I tried to ping from one computer to the next it couldn't
> connect.
>
> Am I missing something?
> Can the cable itself be the source of the problem (they had some
> problems cutting it for me)
> AFAIK what I did was what I've been told by the NET3-Howto,
> (ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up)
> and it didn't work as well. (i assume that's what the RH init script
> does anyway)
>
> Please help,
> Thanks,
> Yoni.
>
> --
>
> The day Microsoft makes something that doesn't suck,
> is probably the day they start making vacuum cleaners...
--
The day Microsoft makes something that doesn't suck,
is probably the day they start making vacuum cleaners...
