[Help Me] Another DGL-4300 problem

Author	All Replies
Bgaimur @comcast.net	[Help Me] Another DGL-4300 problem Before you read the rest, know that this is a problem that developed recently, and I've had the router for ~~ 6 months. Let's start with the problem I'm having: I am receiving high/fluctuating latency to/from my router. I pinged my router for a good while and it seems as though there's something slowing it down. I am not downloading/uploading anything at all. Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time=9ms TTL=64 Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time=20ms TTL=64 Reply from 192.168.0.1: bytes=32 time=22ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=19ms TTL=64 Reply from 192.168.0.1: bytes=32 time=8ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=19ms TTL=64 Reply from 192.168.0.1: bytes=32 time=25ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=13ms TTL=64 Reply from 192.168.0.1: bytes=32 time=18ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time=6ms TTL=64 Reply from 192.168.0.1: bytes=32 time=15ms TTL=64 Reply from 192.168.0.1: bytes=32 time=17ms TTL=64 Reply from 192.168.0.1: bytes=32 time=18ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=15ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=9ms TTL=64 Reply from 192.168.0.1: bytes=32 time=10ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=9ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=18ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=12ms TTL=64 Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time=10ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=9ms TTL=64 Reply from 192.168.0.1: bytes=32 time=15ms TTL=64 Reply from 192.168.0.1: bytes=32 time=6ms TTL=64 Reply from 192.168.0.1: bytes=32 time=14ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=20ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=14ms TTL=64 Reply from 192.168.0.1: bytes=32 time=23ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Reply from 192.168.0.1: bytes=32 time=14ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=20ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Reply from 192.168.0.1: bytes=32 time=19ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Reply from 192.168.0.1: bytes=32 time=12ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=20ms TTL=64 Reply from 192.168.0.1: bytes=32 time=4ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=18ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=6ms TTL=64 Reply from 192.168.0.1: bytes=32 time=12ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=14ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time=22ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=20ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=24ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=13ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=11ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=19ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=8ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=16ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Here's a small sample of what I'm getting when I have the router hooked up. When I do not have the router plugged in, however, the ping is how it should be. Pinging 71.227.18.166 with 32 bytes of data: Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 Reply from 71.227.18.166: bytes=32 time<1ms TTL=128 I think it's obvious what my problem is: the router. Now, I don't really want to go out and get a new one or anything, as I've used it for a while and it's worked. I also have other people using wireless at the moment, so I don't want to interrupt their access either. I've also noticed something rather interesting in the status pane of the router's web manager: Notice the errors on the LAN side of things? I've never noticed that, and I'm almost certain that it never had errors before. I've tried to: 1. Reboot the router/modem. 2. Switch ports in which the Ethernet cord is plugged into on the router. 3. Go back to factory configuration settings. 4. Upgrade firmware to latest version on the DLink website. 5. I've looked through all of the support/FAQ's on the dlink site, but to no avail. 6. I've put the router on it's side (standing up) so it wouldn't get so hot lying down (it wasn't that HOT, simply warm. Comparable to the temperature of a laptop after regular use) 7. Plug myself into the modem directly(the result was that I figured out my ethernet cord/NIC/modem were all fine, and that the router is the real cause of the problems) 8. I've turned on/off almost every setting on the router that I could even consider a factor, and I've even reset to all defaults. With that said, is there any recommendations that anyone can give me? They would all be much appreciated.
Bgaimur @comcast.net	to forum · permalink · 2007-12-10 23:24:28 ·


Monday, 30-Nov 03:45:41	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com.republican-creole page compression OFF