On Sat, Oct 20, 2007 at 08:24:58PM -, Ed wrote:
>
> Hi Andrew,
> You ask great questions - THANKS
I'm just going through the same process I would for my own systems. It
a matter of asking more and more questions until you hit the one that
does it. :)
> Here are some answers.
>
> On the mach
On Sat, 20 Oct 2007 18:00:17 +0200, Andrew Sackville-West wrote:
> On Sat, Oct 20, 2007 at 02:39:20PM -, Ed wrote:
>>
>>
>> Interesting. From the affected machine, I can NOT ping 192.168.1.1 but
>> from affected machine, I CAN ping other machines on my local lan. I
>> can
>
> can your *ot
You could have a bad cable running from the affected computer to the
router. Why not try a cable swap and find out if you can take another of
your machines down?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Oct 20, 2007 at 02:39:20PM -, Ed wrote:
>
>
> Interesting. From the affected machine, I can NOT ping 192.168.1.1 but
> from affected machine, I CAN ping other machines on my local lan. I can
can your *other* machines ping to 192.168.1.1?
I think maybe you've got some architectu
Interesting. From the affected machine, I can NOT ping 192.168.1.1 but
from affected machine, I CAN ping other machines on my local lan. I can
not ping anything on the internet from the affected machine, but can from
any other machine on my home lan. The output of 'route' looks
essentially
[now I'm *really* putting it back on the list...]
On Fri, Oct 19, 2007 at 06:38:28PM -0400, Ed Doyle wrote:
> below is ifconfig and route
>
> Ed
>
> eth0 Link encap:Ethernet HWaddr 00:20:78:1E:66:90
> inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
> UP
6 matches
Mail list logo
