D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: espressoman on May 31, 2009, 06:02:08 PM
-
Ugh! This was a great router until I updated to 1.31. I have an A3 revision DIR-655. Since upgrading to 1.31, I've had nothing but connectivity problems. Wireless seems to stop working after a day or two, a forced reboot (unplugging and plugging back in) corrects it. But, in a day or two, I must repeat. I have two Xbox 360s in the house, and use the uPNP setting on the router (no port forwarding) and they are periodically dropping their xbox live connections. All was well with the previous version of firmware. Now, nothing but connectivity headaches.
I've tried resetting the router and starting from scratch. No dice. What are my options? Do I call DLink Customer Service?
-
May be a bad flash.
Reset the router to defaults by pushing the reset in the back of the router.
After router comes back online flash the firmware again.
-
May be a bad flash.
Reset the router to defaults by pushing the reset in the back of the router.
After router comes back online flash the firmware again.
Done. I'll follow up in a couple days and see if I'm still experience the same connectivity issues.
-
May be a bad flash.
Reset the router to defaults by pushing the reset in the back of the router.
After router comes back online flash the firmware again.
1.3x IS bad flash... :-X
-
1.31 works fine here. Sorry to hear some users have issues.
-
I just posted a new thread about rev 1.31. It doesn't work well for me. How did you make it work, EddieZ?
-
I just posted a new thread about rev 1.31. It doesn't work well for me. How did you make it work, EddieZ?
Pfff..nothing special, to be honest. Just set it up manually. I have changed configs the last few days (AP mode, router mode) and both sitautions is OK. With DHCP using static IP's and in both situations using DNS relay.
To be honest there's not so many things you can do wrong... so if you wanna ask about some specific setting: be my guest.
-
I think some people just have a bad flash the first time or need to reset to defaults before flashing.
1.31 works fine for me too.
-
I think some people just have a bad flash the first time or need to reset to defaults before flashing.
1.31 works fine for me too.
That sounds like perfect conclusion. So sad theres so many bad flash & incorrectly updated devices. :-X
-
Maybe D-Link should improve the instructions on how to flash the firmware on their routers. I really don't think it's the user's fault that the procedure is not being done correctly. Most users do not check/read these support forums until AFTER there is a problem, so most users would not know about the correct procedure to update.
If you look at the firmware update page on all their routers, there is NOTHING suggesting the user should reset the router before and after a flash. In fact, it suggests this:
"Before performing an upgrade, be sure to save the current configuration from the Tools → System screen."
Which tells me, D-Link wants you to save the Config file first, flash then reload the Config file. Every D-Link tech on this board has advised against that.
If D-Link improved these instructions, then there should be far fewer problems.
jB
-
I would like to see the new user registration numbers for after 1.31 was released. It certainly looks like this place got alot busier after 1.31 then when 1.21 was released.
-
Does not have to be a connection between those. Could be ofcourse but you need to count the people that don't appear on the board anymore also... Unless you go and assume they bought another router.
-
Maybe D-Link should improve the instructions on how to flash the firmware on their routers. I really don't think it's the user's fault that the procedure is not being done correctly. Most users do not check/read these support forums until AFTER there is a problem, so most users would not know about the correct procedure to update.
If you look at the firmware update page on all their routers, there is NOTHING suggesting the user should reset the router before and after a flash. In fact, it suggests this:
"Before performing an upgrade, be sure to save the current configuration from the Tools → System screen."
Which tells me, D-Link wants you to save the Config file first, flash then reload the Config file. Every D-Link tech on this board has advised against that.
If D-Link improved these instructions, then there should be far fewer problems.
jB
This is a good tip. Thakns. I'll try to refresh the firmware tonight and keep posted.
-
Does not have to be a connection between those. Could be ofcourse but you need to count the people that don't appear on the board anymore also... Unless you go and assume they bought another router.
You are right, but if you look here and dslreports, there is a lot of the same story: 1.21 fine, 1.31 router freezes.
I will admit I was somewhat wrong about switching routers. I recently purchased a Linksys 610n (am I allowed to say that?). Anyway, that router is by far the worst router I have ever used. My wireless would drop every 30 mins. The 655 is def better than that.
Does anyone have experience with some of the more expensive dlink models?
[Edit] Looking at the more expensive models, it looks like they are also experiencing the issues with DNS relay, atleast the 825 is. I guess those were just bad flashes too :p
-
Hi,
Just a couple cents on the underlying subject....
I think if router companies would spend about 14 cents for a heat-sink and a cooling fan inside these little furnaces, a LOT of these naggy issues go away. The wireless chips overheat REALLY easy and start flaking out, once they cool down, they run fine.
Not just Dlink...but all of them have these issues. Too much heat in too small a space.
SD1
-
Hi,
Just a couple cents on the underlying subject....
I think if router companies would spend about 14 cents for a heat-sink and a cooling fan inside these little furnaces, a LOT of these naggy issues go away. The wireless chips overheat REALLY easy and start flaking out, once they cool down, they run fine.
Not just Dlink...but all of them have these issues. Too much heat in too small a space.
SD1
I have a laptop cooler under mine plugged into the USB port.
-
Put them upright (lights downwards) and there is much more cooling.
-
Isn't the A4 the only model that doesn't have a heatsink? If you look at the 825 board, it looks like people are experiencing this problem with the recent firmware for that model too.
-
I doubt seriously that the firmware changed enough of the unit's functionality that it's now over heating where it wasn't before.
-
I doubt seriously that the firmware changed enough of the unit's functionality that it's now over heating where it wasn't before.
Exactly, and since the A4 is the only model that I don't think has a heatsink, I seriously doubt that before 1.31 it was teetering on the line of stability, and 1.31 pushed it over the edge. That doesn't make sense.
Since the 825/655 both seem to be having issues with their new firmwares, it def seems firmware related, not heat related. They probably share a lot of the same code since they both use the same Ubicom platform.
-
I agree, however the issues with shareport and the port forwarding are likely unrelated. However there was another thread where a user relates his port forwarding issue to Securespot so I'm investigating that aveune since the securespot utility is capable of controlling the firewall from the backend I think.
I'll need to check in to it.
-
I agree, however the issues with shareport and the port forwarding are likely unrelated. However there was another thread where a user relates his port forwarding issue to Securespot so I'm investigating that aveune since the securespot utility is capable of controlling the firewall from the backend I think.
I'll need to check in to it.
Right, I was talking about this thread:
http://forums.dlink.com/index.php?topic=5549.0
users on 825 having lockups with their new firmware unless they turn off dns relay.
-
Well, 2 days since I did a complete reset and re-flash of the firmware. I also turned off DNS relay like others have suggested and so far no lockups or connectivity issues.
-
My router has been working for 24 hours w/o any losing connection problem. What I did is reset the router by pressing the reset button in the back. The DNS Relay is on and it works so far so good.
-
Well, 2 days since I did a complete reset and re-flash of the firmware. I also turned off DNS relay like others have suggested and so far no lockups or connectivity issues.
some have suggested it takes about 5 days for the problems to start,,like some type of memory leak maybe befor the lockups happens. dropped packets, dropped connections & freeze ups.
-
Not sure what it was but after opening up the top for better cooling with fan, 30/30/30 reflash, and turning off dns relay. I can say firmware 1.31 has had no obvious issues reoccur for me. Xbox live signal isnt dropping like before. All settings default except for dns relay.
-
Not sure what it was but after opening up the top for better cooling with fan, 30/30/30 reflash, and turning off dns relay. I can say firmware 1.31 has had no obvious issues reoccur for me. Xbox live signal isnt dropping like before. All settings default except for dns relay.
Are you stating that you have left the cover off the router? Do you plan on leaving it off for good?
-
Maybe. But my intention is to try a laptop cooler powered through the shareport like others have stated and check the temp on the heatsinks. They do get hot to the touch. Hopefully heat is not an issue with this router but it cant hurt to cool it down either.
-
Hi,
Just a couple cents on the underlying subject....
I think if router companies would spend about 14 cents for a heat-sink and a cooling fan inside these little furnaces, a LOT of these naggy issues go away. The wireless chips overheat REALLY easy and start flaking out, once they cool down, they run fine.
Not just Dlink...but all of them have these issues. Too much heat in too small a space.
SD1
meybe all customers will have to crack it open and put some PROPER thermal paste on the processor like this http://www.arctic-cooling.com/catalog/product_info.php?cPath=39_&mID=127
-
meybe all customers will have to crack it open and put some PROPER thermal paste on the processor like this http://www.arctic-cooling.com/catalog/product_info.php?cPath=39_&mID=127
I was actually trying to draw attention to the fact that if the router is overheating - and I'm not saying that it is - then removing the cover is an unacceptable solution.
-
Keeping the hood open is absolutely no solution. A2 is not overheating, it is not even very warm. But manufacturing errors can (and do) occur....