Welcome to the MacNN Forums.

kam61799 · Sep 24, 2003, 08:19 AM

I have the simplest setup imaginable: cable service piped into a D-Link router (DI-614+ to be exact) and then just my single Ti accessing the internet. Everything was a snap to get working and setup, but lately for some unexpected reason I've been noticing a slowdown in my page load times. I'm still getting the same line speed readings from speed test sites like toast.net and dslreports.com, but there is now a definite delay before pages pop open. Just to make sure that I wasn't losing my mind I unplugged the router and ran the ethernet cable straight from the cable modem to my 'Book. Sure enough pages would open nearly twice as fast (e.g. - Apple.com loading in 2 to 3 seconds instead of 10 to 11 over my wireless connection. I tested a bunch of other pages, making sure to clean out my browser cache before making comparisons.). Before you ask, no this isn't a case of a weak signal and the Ti's horrible wifi range: my book is less than two feet from the router and at the same elevation. It makes sense that there will be some sort of speed loss, but waiting twice as long for pages to load is getting a bit absurd. I've done everything I could think off: updated the router's firmware, cleaned out my system caches on the PowerBook, made sure that there is no outside source of interference (cordless phone, etc.), repaired permissions. Everything to no avail. No matter what I do performance through my router still stinks and I'm beginning to wonder if this is just a crap router. Any help would be greatly appreciated.

ghporter · Sep 24, 2003, 02:21 PM

There's a little microprocessor in your router, complete with RAM, buffers and so on. The poor guy could just need a reboot. Every now and then it's a good idea to power cycle your router, particularly when you notice problems like latentcy and DNS errors. It doesn't take much time and even if it's not the solution it doesn't hurt.

kam61799 · Sep 25, 2003, 03:35 PM

Originally posted by GHPorter:
There's a little microprocessor in your router, complete with RAM, buffers and so on. The poor guy could just need a reboot. Every now and then it's a good idea to power cycle your router, particularly when you notice problems like latentcy and DNS errors. It doesn't take much time and even if it's not the solution it doesn't hurt.

Thanks for the reply; I've rebotted this thing at least a dozen times in my attempts to get it to work better. Unfortunately that's not the problem. More and more I'm leaning towards simply picking up a new router.

ghporter · Sep 26, 2003, 10:22 AM

Before you spend more money, here's something else to try. Turn off both the modem and the router. Let 'em sit for several minutes. Turn ON the modem and let it initialize; wait a couple of minutes to let it completely finish. Now, turn on the router and let it do its thing. This allows the modem to properly recognize the router and connect to it.

Some cable providers use the hardware address of the computer connected to the modem for user authentication. If you change what's plugged into the modem, the modem may no longer provide a connection, or it may provide a limited speed connection. The provider can sometimes remotely instruct the modem to verify that hardware address, or to only accept the original hardware connection. If your service agreement doesn't specifically say that you can't use your own networking equipment for wireless connectivity (or security!), then you may need to call their tech support and see what's going on.

kennedy · Sep 26, 2003, 11:20 AM

Also, I didn't see you mention trying different channels... that would definitely be worth a try. Next, if you have a friend with a wireless card in a laptop, invite them over! That'll help narrow down the problem.

HTH. Good luck.

kam61799 · Sep 26, 2003, 03:12 PM

Thanks for the suggestions guys. After messing around with this thing for a couple of days I've pretty much given up on the router (D-Link DI-614+). I've tried unplugging both the modem and router like you suggested GHPorter; waiting as long as ten minutes and trying ever conceivable combination of plugging one in first and then the other; all to no avail. I've checked with my ISP and there is no issue whatsoever from that end. I've also tried every channel and the problem persists across the entire spectrum. Actually I finally let my frustration get the better of me and picked up a cheap Linksys wireless router from a local electronics shop. Of course the new router performs flawlessly so its pretty apparent that there is some sort of problem with my D-Link router. This is the second router I've had from them (the first stopped transmitting a wireless signal) so I'm not too excited about the prospect of them sending me another warranty replacement, but what can you do?

Thanks again for all the help.

ghporter · Sep 26, 2003, 03:42 PM

kam,

That's the most diagnostic, but least cost effective way to troubleshoot a problem. In your case, it turned out to be the best option. I hope you have better luck with your Linksys box than with your D-Link router.

One suggestion: if you don't already, make sure that you plug your wireless router into an UPS. These not only provide power during electrical outages, they also condition what's coming in, preventing outside stresses on power supplies. And keep the router as cool as possible; don't stick it in an enclosed space where it can heat up, since these types of equipment don't cool themselves very effectively.

kam61799 · Sep 26, 2003, 04:03 PM

GHPorter:

You said it - certainly the least cost effective approach (just wish my girlfriend would have chosen her words as tactfully as you did). Actually I was a bit surprised at how great the performance was after hooking up the Linksys router. For all my anal retentive compulsion, I couldn't perceive even the slightest bit of speed loss. As the two defective D-Links were the first wireless routers I had owned (and the only time I had used my PowerBook with a wireless web connection) I just assumed that the slight bit of latency when opening web pages I experienced with them was pretty much par for the course. Imagine my pleasant surprise when I realized I'd been duped all along by shoddy components. Well, wireless surfing is truly a pleasure now (no nagging voice in the back of my head letting me know that pages would pop open a fraction of a sec faster if I just sat my couch potato butt down at the desk) and I'll make sure to take the thoughtful precautions you mentioned to make sure everything continues to run smooth.

Thanks again.