Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Demonized]

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.

[michelle0]

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

[michelle0]

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

[michelle0]

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

[Demonized]

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.)

[michelle0]

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 

[alphanumeric]

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.

[Demonized]

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.

[tbmorris51]

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.

[devoh]

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.

[hfournier]

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

[alphanumeric]

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.

[hfournier]

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.

[ryan200]

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

[mashean]

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.