Strange network problem

[Brian Densmore]

Well it turns out it was an intermittent short in one of the
wires on the cable on the NIC side. Cutting and recrimping
a new connector is all that was needed. Although, yesterday the
box shut itself down and I couldn't get it to come back up until
I unplugged it for 30 sec. We'll see if it happens again. Some 
possible causes here might be:
1) overtweaking the BIOS settings,
2) the shutdown if cpu core gets too high.
I had the problem with my other ABit MB when the shutdown if
core temp gets too high. I don't think that functions works 
properly. I had it disabled on the old one, because it didn't
actually shutdown on temperature. It would shutdown if the cpu
fan indicated it was not running, regardless of how cool the CPU
was. So I suspect same thing may be happening here. Anyone else
think that the current MB makers are overdesigning MBs?

Thanks everyone for the help and suggestions!

Brian 

> -----Original Message-----
> From: Gerald Combs 
> Sent: Monday, August 23, 2004 1:39 PM
> To: Brian Densmore; Kclug
> Subject: Re: Strange network problem
> 
> 
> Brian Densmore wrote:
> 
> > and ifconfig returns something like:
> > 
> > eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
> >           inet addr:172.21.12.2  Bcast:172.21.12.255  
> Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:23
>                                                              ^^
> >           TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:0 TX bytes:6348 
> >           Interrupt:x Base address:0xxxxx
> 
> The ifconfig(8) man page doesn't say what the "frame" counter is for
> (you'd think it would after all these years), but according to the
> net-tools source code it's the output of a variable called
> "rx_frame_errors".  It looks like you have framing errors on 
> your line.
>  Lots of things could cause this, including a bad driver, NIC, cable,
> patch, or switch port.  It _might_ be due to a duplex mismatch, but in
> that situation you usually have frames come through.  A speed mismatch
> might be a possibility as well.
> 
>