Thanks for the great advice as always Charles and Lynn. I hadn't considered the memory or drivers as potential problems. In the past I've had problems finding the right drivers for the Linksys chipset du jour, but when I got one that loaded they had worked fine.
Tonight I'll: 1) test the memory 2) try an alternate driver for the Linksys NICs 3) try different NICs Thanks again. - Todd > -----Original Message----- > From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 14, 2003 10:56 AM > To: Todd Pearsall > Cc: [EMAIL PROTECTED] > Subject: Re: [leaf-user] Dachstein Config, HW Issue or > Comcast Download Cap? Approx 2MB dl Limit > > > Todd Pearsall wrote: > > Now for the problem, for the week or 2 (approx. the same > time as the HW > > swap) I can't download files greater than about 2MB. It > 1st appeared > > because some antivirus downloads were failing and later I > noticed that > > any somewhat large file would just hand during download. > When it hangs > > the cable modem shows no activity. Messages and auth.log are clear. > > > > Due to the timing I assume it's something with the firewall > change, but > > can't image what and I never rule out Comcast messing with things. > > Could a bad NIC cause behavior like this? Other ideas. > > I would suspect a bad NIC or driver. If the box doesn't > crash (sounds > like it's still up if you can check the logs), try the following: > > First, try "kick-starting" the networking with "net reload". In > addition to reloading your firewall rules (probably not necessary in > this case), it will tear-down the low level network setup and > re-build > it. If this fixes your problem, you almost certianly have a > bad NIC or > flaky driver software. NOTE: This will *NOT* tear-down any > interfaces > not directly configured by the Dachstein network scripts (ie dhcp > configured interfaces)...you'll have to do this manually. > > If the above doesn't work, try stopping the network with "net > stop", and > manually removing the ethernet drivers. Then re-load the drivers, > re-start the network and see if things are working again. If > this fixes > the problem, it also indicates a hardware and/or driver issue. > > If you can reboot the box and everything is working OK, the > problem is > not likely to be with Comcast, even if you can't recover connectivity > with the above methods. > > Finally, make sure your new platform is OK. Run memtest86 > for an hour > or so to see if you have any random memory errors (which can > cause lots > of mysterious problems, and are not uncommon on old hardware). You > might also want to do some googling on your chipset. There > may be some > early PCI chipsets/BIOSes that don't quite work right, and > could cause > strange problems. > > You can also try using different NICs, to see if that helps. > > -- > Charles Steinkuehler > [EMAIL PROTECTED] > > ------------------------------------------------------- This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
