D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: gomyway on October 17, 2009, 03:15:08 AM
-
It has been month's and the nightmare still going on. I'm finally pissed off today upon n times of router rebooting, I felt the router ruined my life.
I've left negative feedback on Amazon.com for the product, and will do it on newegg.com, buy.com,etc, one feedback one week, until they provide fix for the firmware.
Hopefully this is getting their higher management's attention.
-
I felt the router ruined my life.
(http://vnutravel.typepad.com/soundoff/images/loser.jpeg)
-
Are you trying to irritate me so that I say something bad to you to give reason to have my post deleted? LOL
-
It has been month's and the nightmare still going on. I'm finally pissed off today upon n times of router rebooting today, I felt the router ruined my life.
I've left negative feedback on Amazon.com for the product, and will do it on newegg.com, buy.com,etc, one feedback one week, until they provide fix for the firmware.
Hopefully this is get their higher management attention.
Good idea! We should all leave negative feed back, maybe that will get Dlink's attention ;)
-
I haven't had any problems with 1.23NA
-
No problems here wih 1.32. So no need for negative feedback.
Sorry
-
Are you trying to irritate me so that I say something bad to you to give reason to have my post deleted? LOL
No...... not at all.
Just can't imagine someone would confess that a , "router ruined my life"
Kinda dramatic, wouldn't you think ?
-
I have big problems after 3 days 12 hours stable. The hole s*** stopped, couldn't even login into my router, had to restart. Thats the first time in over 1 year i had to restart for login, damn f....... firmware v.1.32NA.
Hope they will fix this... so in 3 days i have to restart again... damn s***.. i have web servers running here and game servers.. >:(
-
i have found many things dont work on my 1.32NA FW. my DMZ, Prot forwarding, Virtual Server, just to name a few.
-
For those who haven't had problem with 1.32NA firmware yet, most likely because they just use internet slightly for web browsing/email etc. For that purpose any cheaper router can do.
I've spent more than $150 to buy this router to replace my old router, and I had been satisfied with the investment for one year till I upgraded to the firmware 1.32. It is NOT a good excuse to say that the firmware doesn't need fix because some of the customers don't have any problem..
-
For those who haven't had problem with 1.32NA firmware yet, most likely because they just use internet slightly for web browsing/email etc. For that purpose any cheaper router can do.
I've spent more than $150 to buy this router to replace my old router, and I had been satisfied with the investment for one year till I upgraded to the firmware 1.32. It is NOT a good excuse to say that the firmware doesn't need fix because some of the customers don't have any problem..
I bekieve is more like most of the customers don't have any problem..
-
For those who haven't had problem with 1.32NA firmware yet, most likely because they just use internet slightly for web browsing/email etc. For that purpose any cheaper router can do.
LOL ;D, apart from 4 people using internet (including two teens with heavy gaming and torrent habits) my server setup hosts three websites with moderate traffic and internal (LAN) HD streaming. All at once.
So if that's a light weight user I wonder which setup is considered a heavy user like perhaps you yourself seem to be ???
-
I don't understand, who are those people coming to the product forum and show their gratitude every day for their router is stable. Isn't it what your money paid for?
Even if I'm the only one has this problem, should they fix the problem for me? That being said, I'm not going to waste time here any more and will just do what I'm supposed to do, then put the router on ebay.
-
My rebooting problems lasted about 1-2 Weeks till I overcame my lazyness and reconfigured all settings from the ground up after a complete hardware and software reset. Since then the router has been working stable.
-
My rebooting problems lasted about 1-2 Weeks till I overcame my lazyness and reconfigured all settings from the ground up after a complete hardware and software reset. Since then the router has been working stable.
Good to see it worked for you.
Adjusting setting too much is what I have been thinking is some of the people's problem.
They go in and start adjusting things and adjusting things and adjusting things then do not remember what all they adjusted so the problem never gets resolved.
You should always try one change and if it does not solve your problem then put that setting back and try another....rinse and repeat until you find the one that solves your problem.
-
I don't understand, who are those people coming to the product forum and show their gratitude every day for their router is stable. Isn't it what your money paid for?
Even if I'm the only one has this problem, should they fix the problem for me? That being said, I'm not going to waste time here any more and will just do what I'm supposed to do, then put the router on ebay.
The people that are here with fully functional 655's are here to help you, since there is more then an odd chance there is a configuration/network issue bothering you. It's turning the world upside down to say that those with working devices are the odd ones out.
-
I bekieve is more like most of the customers don't have any problem..
point,
there is a historical problem with 1.32 that even DLINK has admitted to and haven't a fix yet. They even closed the last HUGE thread about it with a closing admission:
http://forums.dlink.com/index.php?topic=7588.0
Ken
-
The closing statement for the previously mentioned thread about bad 1.32 fw
http://forums.dlink.com/index.php?topic=7588.120
I'm locking this thread. There has been 0 useful posts made here. We understand that your routers are not working properly. We are working on a firmware to address this issue. I can not give you a timeframe for completion as I do not have one to give.
For those of you that continue to suffer with unusable routers do to firmware failure I suggest you contact technical support and request a replacement that has the previous firmware version. For now this is all we can do.
-Lycan.
Although I completely disagree that there were "0 useful posts", as I found them VERY useful in preventing me from upgrading and ruining my rock solid 1.21 config.
I think they were afraid of lost sales due to the number of people posting major issues that they were not addressing. I'm sure others, like myself, research forums before making a purchase of this nature and that forum did NOT shed a good light on the fw included in recent 655s.
BTW, DLINK if you're reading this, closing threads does not make the problem go away. It just makes you look like you don't care. Don't get me wrong, i LOVE my DLINK products, but issues like these have me concerned.
Ken
-
FYI, it looks like they have a rev in beta that has helped some a little:
http://forums.dlink.com/index.php?topic=8931.0
I don't dare try it until I see EVERYONE is happy with it.
Ken
-
FYI, it looks like they have a rev in beta that has helped some a little:
http://forums.dlink.com/index.php?topic=8931.0
I don't dare try it until I see EVERYONE is happy with it.
Ken
A patient man, I see. You will need it....
(explaination: not because of Dlink but the first network device without a single complaint is still in the eternal design phase.)
-
I know never to expect perfection in any device design. I simply meant the obvious hardcore problems like reboots and net loss. 1.21 is not perfect, but it doesn't cause me headaches like that either. Little things I can deal with. But with 1.32, these are major issues, not minor.
I was looking to upgrade fw for Securespot, but not at the peril of my stability.
At least they are working on it :)
-
My rebooting problems lasted about 1-2 Weeks till I overcame my lazyness and reconfigured all settings from the ground up after a complete hardware and software reset. Since then the router has been working stable.
I did the same thing. Reset to factory defaults, re-flashed with 1.32NA over a wired connection, and reconfigured all settings again manually. Shareport and Upnp is now working for me. Previously Shareport would stop working and I had to manually port forward for bit torrent to work. In my case I think I had a bad flash when I initially went to 1.32NA. I shouldn't have had to flash twice with the same firmware but I'm glad I did it now.
-
I know never to expect perfection in any device design. I simply meant the obvious hardcore problems like reboots and net loss. 1.21 is not perfect, but it doesn't cause me headaches like that either. Little things I can deal with. But with 1.32, these are major issues, not minor.
I was looking to upgrade fw for Securespot, but not at the peril of my stability.
At least they are working on it :)
1.21 caused me lots of issues, 1.32 is flawless (although sometimes it just looses track of system time with an ntp server configured...). So there's mixed feelings.
-
Talked with tech support this morning.
They suggested changing my wireless channel from 6 to 1,
changing Beacon to 50
changing RTS threshold to 2307
changing Fragmentation threshold to 2306
Will watch this for a while and see if internet slowdowns stop and will post back as I gather data.
10-29 update: Well I am on Day two with the above changes and so far no slowdowns, no need to reset.
Running Windows 7 Ultimate on 5 computers, and WHS with PP3, a skype adapter, and a ABN alarm adapter.
-
For those who haven't had problem with 1.32NA firmware yet, most likely because they just use internet slightly for web browsing/email etc. For that purpose any cheaper router can do.
I've spent more than $150 to buy this router to replace my old router, and I had been satisfied with the investment for one year till I upgraded to the firmware 1.32. It is NOT a good excuse to say that the firmware doesn't need fix because some of the customers don't have any problem..
I have the issue and I am doing NOTHING special. No QOS, no advanced DNS... It is setup to just be a wireless N access point with firewall with some hardwired connections. I go between 7 and 10 days before I have to power cycle it. When it dies I can not even get to the web interface. So I do not believe that you even have to be doing fancy stuff with it. I bought it because of it's rep at the time.. I believe the best action at this time is for EVERYONE who has this problem to open a ticket on their support page. If you go the route of leaving negative feadback on all sites.. and get people to stop buying it, DLink will just discontinue it.. They only have incentive to fix it if it is an active seller for them.
-
Just adding my name to the list of people with problems.
The router worked fine with 1.21, never had an issue. Since upgrading the firmware, I keep loosing connectivity. I have to power cycle the router on an irregular basis. Some times it lasts a week, some times only a day.
Also noticed that the router loses track of time. I'm guessing that the clock stops ticking when the router goes bye-bye. I'm going to keep checking this every time I have to power cycle to see if I'm right.
Following advice hear, I've done a factory reset and re-flashed firmware. We'll see if that makes a difference. I've also turned off SharePort and SecureSpot.
If I don't see an improvement, then I may try the beta.
A2
1.32NA
Using a wired connection the majority of the time. However, when connection is lost, wireless won't connect either. Not all computers seem to lose connectivity at the same time. Unfortunately, power cycling the router does break everyone's connection.
Win7 Business
Win7 Ultimate (mine)
Win Vista Business
Windows Server 2003
WHS
--
Henri
-
There is no battery to retain the time so if you power cycle the router the time and date will get reset/lost and you will have to set it to the correct time again. The way around that is to enable the NTP server under Tools > Time so it automatically corrects the time after a power cycle.
-
I had turned NTP off some time ago because it wouldn't handle DST properly. I turned it on again and checked Enable DST and sure enough, the time was off by two hours. But I noticed the DST start and end settings weren't what I had set (weird), so I set them again and hit save and finally the router is showing the correct time. I'll see what happens after Nov 1.
-
well i had some issues with coming from 1.31 to 1.32na. i had backed up my settings and reloaded my config and they said they were set but obviouslly they weren't so i reset the router to defaults and set the settings again from scratch and now everything seems to be working fine.
those who don't like 1.32na why not go back down to 1.31 if it had no problems? you can downgrade, you just can't go below 1.3
-
It's unfortunate that Dlink causes many problems with their firmware updates. I'm experiencing the same thing with my DIR-655. To be honest, I had a DGL-4500 prior to this and they released buggy firmware to it as well. Not looking good.
-
tbmorris51,
Any more update?
I would like to try these settings too.
Talked with tech support this morning.
They suggested changing my wireless channel from 6 to 1,
changing Beacon to 50
changing RTS threshold to 2307
changing Fragmentation threshold to 2306
Will watch this for a while and see if internet slowdowns stop and will post back as I gather data.
10-29 update: Well I am on Day two with the above changes and so far no slowdowns, no need to reset.
Running Windows 7 Ultimate on 5 computers, and WHS with PP3, a skype adapter, and a ABN alarm adapter.
-
This is not a cheap router and has been designed with many good features for modern computing needs.
I would think, that Dlink does not want a bad name though all these items that are broken in firmware build 1.32NA. But, they seem to have this big corp attitude, that they do not care what poeple are saying about this product.
We have been using this router for an IP-PBX product that we market and have had nothing but grief with it, not being able to handle the SIP and tunneling correctly. This is due to the application gateway feature not doing it job correctly in controlling the packets across the NAT. If the router resets, which it does every few hours. The only way to get it working again is to change the static IP address of the IP PBX. WHAT a great pain... This has been reported to Dlink Tech support, who again give you the attitude of nothing is wrong with their product and are NO help at all.
Therefore, we are replacing all DLink equipment and would not recommend their products to anyone. You will see them on ebay as they are only fit for the casual computer user. who just surf the web :( :( :( :( :( :( :( :(
-
This is not a cheap router and has been designed with many good features for modern computing needs.
I would think, that Dlink does not want a bad name though all these items that are broken in firmware build 1.32NA. But, they seem to have this big corp attitude, that they do not care what poeple are saying about this product.
We have been using this router for an IP-PBX product that we market and have had nothing but grief with it, not being able to handle the SIP and tunneling correctly. This is due to the application gateway feature not doing it job correctly in controlling the packets across the NAT. If the router resets, which it does every few hours. The only way to get it working again is to change the static IP address of the IP PBX. WHAT a great pain... This has been reported to Dlink Tech support, who again give you the attitude of nothing is wrong with their product and are NO help at all.
Therefore, we are replacing all DLink equipment and would not recommend their products to anyone. You will see them on ebay as they are only fit for the casual computer user. who just surf the web :( :( :( :( :( :( :( :(
If you rely that much on equipement and service you might refrain from saving every penny and get a pro device with matching service contract. This is still a home router and you will not find many IP PBX's is home environments. And maybe your IP PBX sux....who knows. ;)
-
I have the same DMZ, port forwarding, and lock ups that others have documented. I have made several valuable and helpful posts about this - including that disabling DNS Relay resolved the lock up specific issues, but still makes the router useless to me if I cannot use any of the advanced networking like DMZ or port forwarding. To date, D-Link CHOSE to kill that thread completely.
I do believe we need to take further action. Negative word of moth does wonders and seems unfortunately necessary at this point. Regardless of price, we all spent money for a product that simple does not do what is expected. It used to, until D-Link provided additional features (that it advertised) and simply do not work. I upgraded my firmware because I had a need for removable media. I was FORCED to upgrade further because no-one would addmit or address the lock ups many of use were experiencing. It was that second firmware upgrade that killed my port forwarding and that should have immediately been adressed by D-Link. This was their flagship router for this segment of the market and they seem to have abandonded it and their customers who bought it. Looks like it is back to Cisco/Linksys for me - AND, though this router was for my personl/home use, I do use routers and switches in my everyday life in the IT business. Guess you can bet where my future purchasing dollars and recommendations to other customers is going!
-
Getting disconnected very often, router restart on its own, and web UI hang after upgraded to this firmware. I wonder what they did with this firmware, and why no fix available yet?
-
Try to reset to factory defaults, reflash the firmware and reconfigure manually (do not load the saved config). In some cases the upgrade is not perfomed well. Maybe a firmware thing, maybe a firmware loader issue, I don't know but it does happen some times.
-
Good advice EddieZ, re-flashing to 1.32na fixed my Shareport problems. IMHO it was well worth the time to do it all over again. The only thing I'd add to what he said is don't flash it over a wireless connection.
-
Good advice EddieZ, re-flashing to 1.32na fixed my Shareport problems. IMHO it was well worth the time to do it all over again. The only thing I'd add to what he said is don't flash it over a wireless connection.
Very good addition! the manual does say so too, but who reads those anyway... ;)
-
Two days after doing the factory reset and reflash of 1.32NA, the router went south again and had to be power cycled.
But, after that, I turned off DNS relay and haven't had a problem since. Waiting to see how long it will last...
-
Two days after doing the factory reset and reflash of 1.32NA, the router went south again and had to be power cycled.
But, after that, I turned of DNS relay and haven't had a problem since. Waiting to see how long it will last...
Was this 132NA or the new beta 9 (ftp://ftp.dlink.com/Gateway/dir655/Beta/Firmware/dir655_fw_132b09NA_beta.zip) that just came out?
-
Was this 132NA or the new beta 9 (ftp://ftp.dlink.com/Gateway/dir655/Beta/Firmware/dir655_fw_132b09NA_beta.zip) that just came out?
1.32NA (I haven't dared try the beta)
-
Well....the beta is supposed to fix the DNS relay issue.
I am running the beta without issue of any kind so far.
-
Well....the beta is supposed to fix the DNS relay issue.
I am running the beta without issue of any kind so far.
OK, great! I hope that's it then. The beta feedback thread seems to reflect the same. Please post there in the next few days. In my case, it sometimes took a few days before it locked up.