D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: bladefd on March 20, 2011, 03:24:37 PM
-
Hey, I just registered, and was seeking some help w/ the DIR-655. I saw it was on sale on Newegg for around $50 w/ a $15 promotional code. I decided to purchase that, and I have had it for the past 4 days. Firmware is Version 1.32NA. Hardware version A4.
Unfortunately, it has been crashing once a day (I noticed it usually crashes between a window of 4:30pm and 6:30pm if that makes any difference). What happens is that it starts to slow down my entire net. That lasts for about 5-10 minutes before my entire net crashes to the point that I can't even access my router. I have to restart the router and cable modem afterwards..
Today, after the crash, I decided to connect my own primary computer straight to the cable modem. Internet started to work while connected straight to cable modem, but it was pretty slow. I did not run a speed-test so I don't know the exact speeds it was getting.
Here's how my network is setup. Before I get to it, I want to say that it is a bit messy. I am removing one of the routers (the Ativa one). Goes like this:
Motorola SB5101 Cable Modem from Comcast in the basement
From Cable Modem, it goes directly to my Dir-655 right there in the basement.
From Dir-655, here's how the 4 ports are split.
1) straight to my own primary computer from the basement to computer on first floor
2) straight to other computer from the basement to first floor
3) to Alvoi Phone adapter (that goes to the phones)
4) goes to another router (Motorola VT2542)
The Motorola VT2542 goes to the 3rd floor. It has 3 ports connected.
1) goes to computer on the 3rd floor
2) goes to another computer on 3rd floor
3) goes to Ativa AWGR54 - main reason why it is connected is for wireless on the 3rd floor, which weakens from the Dir-655 down in the basement. Fortunately, it is not necessary. I just removed it just now after this 3rd crash in 4 days. I won't connect it back and see if network crashes again.
Before I brought the D-link Dir-655 into the equation, I had a Linksys BEFSR41 version3. I never had this issue. The network was setup slightly different: Cable Modem to Linksys router. From the 4 ports, 2 of them went to 2 computers and 3rd went to Ativa on 3rd floor. 4th port went to Motorola VT2542. The Motorola VT2542 had 2 computers connected and 3rd was Alvoi Phone Adapter (4th port empty). That setup worked without a problem. It was basically the same as it is now except it went Motorola to Alvoi, but now they are both on their own separate ports of the DIR-655. I had a total of ~5 crashes in the last 3 years. Unfortunately, the BEFSR41v3 is dead..
Any ideas on what I should try next to further figure out the issue? The only changes I made was take the Ativa router off and restart the modem/router. When the internet works, it works without a problem; it is only when the crash starts up. As I said, it starts by first slowing down my entire net before completely crashing. The amount of time between the slowing down of net and complete crash is about 10-15 minutes.
Could the router be bad? It is brand new, 4 days old.. I still have the box and cd/wire/etc. Only thing gone is the outer plastic wrapping from the actual box. If you need any more information, let me know.
I also changed my DNS settings ( http://www.opendns.com/support/article/219 ) after my first two crashes. Somehow, the internet crashed today also so I don't know if DNS is necessarily the issue.
Thanks fellows!
-
Step one would be to update the firmware. The current version is 1.35NA.
There seems to be a glitch with the router finding the update through the tools menu, so just go straight to the D-Link website and do the download.
There are significant changes so it's been recommended not to do a restore of your settings afterwords, just reconfigure.
Try that and see how it goes.
-
Are there any log entries regarding this crash or router restart during this time frame?
Before you update,
I recommend the following to test:
Turn off ALL Wireless devices.
Reset the router to factory settings.
Turn off QoS.
Use ISP DNS addresses.
Change the WiFi mode from Mixed to Single G or Mixed G and N if you have devices supporting N mode.
Turn on one of the devices that your seeing a crash or disconnection on and test it out for a day or time frame that you can do this. Start adding devices to the connection one at time and test the router.
Update as a last resort before calling DLink.
-
Are there any log entries regarding this crash or router restart during this time frame?
Before you update,
I recommend the following to test:
Turn off ALL Wireless devices.
Reset the router to factory settings.
Turn off QoS.
Use ISP DNS addresses.
Change the WiFi mode from Mixed to Single G or Mixed G and N if you have devices supporting N mode.
Turn on one of the devices that your seeing a crash or disconnection on and test it out for a day or time frame that you can do this. Start adding devices to the connection one at time and test the router.
Update as a last resort before calling DLink.
Unfortunately, the router doesn't have the logs from the crash yesterday. It has not yet crashed yet today so I don't have any current logs since that last crash.
I tried factory settings after the first crash. It still crashed the 2nd time.
I always had QoS off since after the first crash. I also used to have ISP DNS addresses until after the 2nd crash. Only then did I change to OpenDNS.
If it crashes again in the next 2 days, I will be sure to get the logs and I will try with wireless turned off completely for another 24hours.
Do you think I should just get the router replaced from Newegg instead of calling D-Link? I read post after post on multiple boards of people complaining about the customer service from D-Link and their RMA process. I knew going in about that image. I am going to see if the router crashes again; it has gone about 28 hours straight without a crash so far. Newegg still has the 30 day return policy (7 days have gone by so far since I placed the order). I still have my original box, pamphlet, cd, router wire and router itself along with the UPS box.
-
If it crashes again and if you want to, do the FW updated...crashes again, I would return it to NewEgg and get a replacement or something different. Keep us posted on how it goes.
-
If it crashes again and if you want to, do the FW updated...crashes again, I would return it to NewEgg and get a replacement or something different. Keep us posted on how it goes.
Update
It crashed again today so I turned off wireless completely. Trying it for another 24-30 hours to see how it goes with no wireless at all. Will update again after that time-frame. I will probably try firmware update if it still crashes again in the next 24-30hrs. Thanks for the help so far
-
Update
It crashed again today so I turned off wireless completely. Trying it for another 24-30 hours to see how it goes with no wireless at all. Will update again after that time-frame. I will probably try firmware update if it still crashes again in the next 24-30hrs. Thanks for the help so far
I'm experiencing a similar situation here as well with firmware 1.12NA at the same time of day. I haven't had an issue with this firmware in the entire time that it's been installed. What I'm noticing on my side of things is that my router will say that it's connected, but my desktop reports that it is not. A release/renew on the router hasn't failed to fix it yet.
-
BTW - I completely forgot to post this, but I took screenshots of my Cable Modem's logs page. The timings on the logs are out of whack for some reason, but I think those errors came up during the times of crash (I accessed the cable modem a short time after the crashes). A lot of the errors are repeated multiple times; I reported this to Comcast, and they told me that their own system doesn't show any problems. They ran some systems checks, and it all came out normal on their end. Maybe these logs could help or maybe not:
http://img17.imageshack.us/g/downstream.jpg/
Direct links to each image:
http://img17.imageshack.us/img17/9853/downstream.jpg (http://img17.imageshack.us/img17/9853/downstream.jpg)
http://img14.imageshack.us/img14/7567/routerlog.jpg (http://img14.imageshack.us/img14/7567/routerlog.jpg)
http://img508.imageshack.us/img508/6071/routerlog1.jpg (http://img508.imageshack.us/img508/6071/routerlog1.jpg)
-
Check the cable line comming from the telephone pole or ground hub. Make sure the wire is good and if there are any splitters on the line, take them out if you can, fewer the better or none. Signal quality on the line can impact network performance. ISP will always say theres nothing wrong on there side.
-
Check the cable line comming from the telephone pole or ground hub. Make sure the wire is good and if there are any splitters on the line, take them out if you can, fewer the better or none. Signal quality on the line can impact network performance. ISP will always say theres nothing wrong on there side.
I doubt it is the cable modem because about 4 days before I bought the router, my original Linksys router was dead. Before that, internet was perfectly fine. The Linksys router stopped working, and it still doesn't work. These crashes only started up once I plugged in the DIR-655.
Update:
Well, it's been about 45 hours without a crash yet with wireless turned off. The longest I have gone so far without a crash was around 50 hours (before wireless was turned off). If it still doesn't crash by tomorrow evening, I will turn wireless back on. Try that for another 48hours. I am pretty sure I didn't change any other setting in my router, but I can't recollect right now if wireless is the only thing I changed since the last crash. Dang it, I should have written it down somewhere. :-[
btw - I found a couple other threads of people that had same issues almost 2 years ago.. Doesn't seem like the problem was ever fixed..
http://forums.dlink.com/index.php?topic=5575.0
http://forums.dlink.com/index.php?topic=5281.0
http://www.dslreports.com/forum/r22752223-DIR-655-1.32-firmware-DNS-relay-issue-fixed-
-
Ok, once you turn the WiFi back on, just connect 1 wireless device and leave off the others and see how it goes...Looks like the wired is good. Now to see if Wireless will work with just 1 device and go from there.
-
Ok, once you turn the WiFi back on, just connect 1 wireless device and leave off the others and see how it goes...Looks like the wired is good. Now to see if Wireless will work with just 1 device and go from there.
Update:
My D-Link crashed with only one wireless device on Saturday (which is my laptop but it wasn't on much anyways while the DLink wireless was on). Afterwards, I noticed that my second router (Motorola VT2542) had wireless on against my knowledge. I thought that was where the issue was so I turned off the wireless on that Motorola router, leaving only the DLink wireless on. Internet crashed once again last night after about 2 full days of no issues at all. I had to restart it. After restarting, things are fine right now. It is getting a bit frustrating though. I have until the end of this week to get the router replaced or to get a refund ($8 restocking fee). Thoughts?
I also noticed another issue. When I turn on bittorrent, my internet surfing SIGNIFICANTLY slows down. I kept a close eye on the torrent (one torrent running total) - the download speed was about 500kb/sec with uploading going at around 20kb/sec. It took a while to load up ALL websites that I tried. Once I lowered the download cap to 400kb/sec, things were loading a bit quicker. As soon as I turned it off, websites suddenly started to load up normally. Why does the throttling only happen with bittorrent but not other downloads? If I am downloading something through mozilla at 2mb/sec or through mIRC at 1.5mb/sec, all websites load normally while downloading. The only thing that I can see is the port. I have bittorrent port at 24537 and mIRC at 6667. Not sure about mozilla (maybe 80?). I don't know if a different port would solve this issue.
-
I would set up ALL of your devices for Static reserved IP address in the router next.
What Wireless mode are you using now? Single mode G or N?
-
I would set up ALL of your devices for Static reserved IP address in the router next.
What Wireless mode are you using now? Single mode G or N?
The mode is "Mixed 802.11n, 802.11g and 802.11b"
I am about to set all devices to static reserved ip address. Should I set it through windows or through the router? The DIR-655 has "Add DHCP Reservation". I could provide the info for each computer's MAC address or should I set it through Network Connections in Windows 7?
-
Set it on the Router, much less work. Keep the Windows machines as DHCP. If you have no B wireless items use the G and N option. The set DHCP reservation is what you want to use.
-
Set it on the Router, much less work. Keep the Windows machines as DHCP. If you have no B wireless items use the G and N option. The set DHCP reservation is what you want to use.
Okay well, I decided to do factory default. Then I changed dns to OpenDNS and set all of my windows machines under DHCP reservation. I also made the wireless mode to 'G and N' option since I don't have any B wireless items. I made sure Advanced DNS was off and also turned off QOS. I did not change anything else (not even the time, I kept the time what it already was after factory default). After about 40 hours of stability, it crashed once again.
This time, I even took off my Motorola router entirely. I had the following 4 things connected to the Dir-655:
Computer A
Computer B
Computer C
Alvoi Phone Adapter
Once again, things started to slow down before it crashed entirely. Finally, it crashed. When it had crashed, I pinged my router's ip and cable modem's ip. I received all packets back from cable modem but nothing from router at all. Only way to fix it is by resetting everything
-
Update:
I also thought I should try the latest 1.35NA firmware so I put that on about 2 hours ago (used to be 1.32NA). I will see if that helps at all. It's been good so far (had wireless going and computers all at once, no crash or slowdown yet). This is pretty much the last thing I can really try that may or may not help from what everyone mentioned in the rest of the thread.
-
Under advanced wireless is your enable extra protection checked or unchecked?
-
One of the last updates:
After updating firmware, it seemed to have become a lot more stable until it crashed again on Monday. I pulled out the 2nd router (Motorola one that I got from Vonage), and tried the Ativa router in place of the Motorola one. Again it crashed every 5 minutes so I took out the Ativa one too. Nothing has crashed at all since Monday when I took out the Motorola/Ative out. I think I may have figured out where the problem is. It crashes only when I connect another router to D-Link.. Most likely it is not the Motorola router or Ativa since I tried them both separately; same issues. Then I realized that the one constant was the Allvoi Phone Adapter. Every single time that my D-Link crashed, it was with the Allvoi Phone Adapter connected. It is terrible and screws up my whole network when another router is on the network. With 4 computers in the house, I don't have a choice but to add another router...
Are there any other decent VOIP services I could switch to? Vonage costs $25, Verizon landline is like $30 without any long-distance phone. Is Vonage the best one in that range? I hate how Vonage throws on mandatory extra costs after saying it is only $25 per month to bring the prices up ($2.89 a month for 911? $1.99 regulatory fees? $2.91 for some federal program fee? Seriously?). False advertisement. :-[
-
If you never heard about ooma I would suggest you give it a look. You can buy them from Costco too which I think then qualifies for unlimited return thing in case it ever breaks or they go out of business. Around 200 for the base unit, then around $3.50 a month for basic service which includes long distance and caller id number. Ive had them for around half a year and once all the kinks were worked out its been pretty nice.
-
@ Bladefd
Glad you found the cause of the issue.
I've been using MajikJack for a while now. No issues. Not sure if thats something you'd want to research. Works good for me and cheap.