D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: phive0 on March 13, 2010, 05:38:27 PM
-
I recently upgraded my A3 DIR-655 from 1.32NA to 1.33NA. Why does the web configuration still show 1.32NA with a build date of 2009/7/9 is loaded?
I have flashed the router twice and powered it off several times with no change in the result.
And yes, I did flash with 1.33NA (filename: dir655_firmware_1.33NA.bin).
-
Just to make sure you were getting the correct file.
CLICK HERE (ftp://ftp.dlink.com/Gateway/dir655/Firmware/dir655_firmware_133NA.zip)
-
I just reflashed with the linked file. Same results even after resetting the router by holding the reset button in for 10 seconds while it is powered up.
-
I have the same problem. Just bought the router a few days ago, it came with 1.32NA and I can not upgrade to 1.33NA no matter what I try. Why is that.
-
I just tried flashing a 1.33 beta variant and it didn't load either...
-
Flashing over wired or wireless connection?
-
Flashing over wired or wireless connection?
Wired. Tried with IE8 and Firefox, Windows XP and Linux...
-
What exactly happens before and during the flash?
What do you see in the browser?
-
OK. Problem solved.
http://forums.dlink.com/index.php?topic=11844.0 (http://forums.dlink.com/index.php?topic=11844.0)
Apparently, holding the reset button in for 10 seconds doesn't work all the time...
-
Apparently this post solved my problem: I think if I recall similiar thread from a couple/few weeks back...somebody suggested holding the hard reset button in for like 30 seconds....then unplug the router for a minute or two...then power it back on and try to flash from that point....I am now using 1.33NA! Thanks. :D
-
Another way I found to apply the 1.33NA firmware was to simply reset the router to its factory defaults via the web interface. After that, reload your settings file.
However, I have had major problems with this firmware update in regards to using the network Time protocol option in conjunction with daylight savings time applied--my location is Vancouver Canada daylight savings started today.
The router went into a continuous reboot cycle. Only after disconnecting the WAN port did it settled down. Apparently the router has a real problems when it comes to NTP pools [groups of time servers at one address with multiple IP's].
Even after rolling back the firmware to 1.32NA. The timestamp on the logs and parts of the web interface are out by one hour.
Before the upgrade of the firmware everything worked fine. This is the first and only problem I've had. In short, unless you have a good reason. Pass this version of the firmware by and wait for the next.
Patrick
-
Yeah, I was trying to update to 1.33NA because of the problem with DST. Using 1.32NA, every time I went into Tools>Time and tried to set the DST date as the 2nd Sunday in March the router kicked me back out to the logon page. It didn't exhibit the continual reboot thing, but keep in mind this was with 1.32NA.
Thanks for the "headsup" on 1.33NA. I'll wait for a more stable update. :'(
-
Yes, other people are having the same issue are appearing in the form now. This router has been on the market for a number of years and one would think these fundamental problems would be addressed.This is actually a large problem for many people as it throws off the router's scheduling feature.
The very odd thing is, I bought the router in July of 2009, daylight savings had already started, and upgraded to the then current version of firmware 1.32 NA with no trouble at all. Time remained correctly synchronized while using the NTP server and when my region went back to standard time. However, even after rolling back the firmware from 1.33 NA to 1.32 NA the time now lags by one hour in the logs and schedule. The only place in the time reads correctly is in part of the routers web interface namely in TOOLS -> TIME .
A letter has already been written to D-Link ( I just use the feedback option available on the main D-Link web site. ) and will keep watching the forum in hopes that this issue is resolved.
Patrick