just a thought here. I used to have problems with pings in rh 6.2. Actually
the prob was DNS. A quick fix to check is to give a name of ip dest machine
at your hosts file. So if you want to ping host A from Host B, at the host B
/etc/hosts file, just give a name for Hosts A. If not, you'll see huge a
delay. And if you actually remove the hostname from hosts file, you would
not be able to even ping the hosts own interface. A permanent soln would be
to point your resolv.conf file to a DNS but make sure it can reach this DNS
or else same prob again. :)
Wong.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Matias Freytes
> Sent: Friday, May 19, 2000 3:21 AM
> To: Donald Becker
> Cc: [EMAIL PROTECTED]
> Subject: Re: ping problems on a 4 PC eth
>
>
> > > Inter-| Receive
> | Transmit
> > > face |bytes packets errs drop fifo frame compressed
> multicast|bytes packets errs drop fifo colls carrier compressed
> > > eth0: 4440898 24078 202 0 0 202 0
> 0 235915 2821 0 0 0 32 18 0
> > > eth1: 215799 2517 0 889 0 1779 0
> 402 1384858 1991 0 0 0 0 0 0
> >
> > That's a *lot* of error, with many corrupted packets.
> > Either you have a bad cable, or some host is set to full duplex.
>
> It's working, at least for the last 30 minutes. We just switched cables
> from one connection to another:
> cable PC1 to PC2 used in PC3 to PC4, etc.
>
> Ok. We'll have to move to baseT.
> Thank you.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
