D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: sammy225 on October 20, 2011, 07:33:47 AM
-
I recently purchased the DIR 655 however it is two firmware updates behind. I see from the instructions and elsewhere that once updated it cannot be reversed. Besides the feature updates are the bugs sufficient enough to warrant updates? Should I just go for the first one or take a chance and do the latest as well? Anyone do the updates and regret it afterwards?
-
I recommend using the router out of the box as is unless you are experiencing any problems, then I would trouble shoot the problem before updating FW. If it works, DON'T FIX IT!!! My 2 cents.
-
In a word? No
-
Which version did you buy? A or B?
-
Dunno
What's the difference?
I bought this one from Amazon: D-Link DIR-655 Extreme N Gigabit Wireless Router
-
Look under the router at the sticker underneath, should have hardware version.
-
Its a B1 - FW 2.00NA unit
-
I would update to the newest one, there are a few changes in there to make the router work better.
-
Well its 2 votes to 1 against so things are working well for me so until I hear otherwise I will stick with the factory installed release.
-
Keep us posted on how things goes. Enjoy.
-
Thanks! Since you asked.....I will say it is much more stable and connects easier on just a "n" network. "b" and "g" as well as "n" (default setting) disconnected me from wireless activity from my network at least once a session but kept me fully active on a 'direct connect' Ethernet line from the Dlink. The fix for that was to unplug the DIR-655 from its power cord and plug it back in (reboot). Neither of the two firmware updates appear to comment or fix this issue so I will leave it like this.
-
I might venture to say there isn't a FW bug rather than a possible configuration issue. The router should not need any rebooting after it's online and working. Maybe someone could review your router settings with you using teamviewer.com (http://teamviewer.com).
-
^^^ I can't agree with you. I picked up this tidbit of info from another poster on a different thread and though they suggested just using the 'g' network for the same issue (immediate disconnection from the network to the point where you had to 'reboot' the Dlink), I decided using just the 'n' network and it hasn't lost a beat yet! Now it takes 1-2 seconds or sooner to connect the wireless node to the Dlink whereas it took 20-30 seconds before. That is a pretty clear configuration change for the better if you ask me! It has been stable since making this change in about 10 sessions.
-
Any other WiFi routers near by. You can see this behavior with other WiFi routers near by, specially if there all using the same G mode and the channels are clogged up. Review the 855 forum, theres a guy there that lives in a Apt complex and he's dealing with the same issues, even on N mode. Lets see what you have around you. I don't think this is a FW issue, just yet. :-\