D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: jdrom on May 29, 2009, 09:51:10 AM
-
I have no idea if it'll fix everyone's problems but it fixed my port forwarding/virtual server issues.
Here's what I did:
1. Press reset button until the lights turn off and on 3 times
2. Restore factory defaults
3. Re-flash 1.31 firmware
4. Restore factory defaults
5. Repeat #4
6. Configure everything manually, rebooting whenever it asks.
This was all done using Internet Explorer 6 I think that's a key point here, since I originally tried with IE8 and Firefox without success.
Everything seems to be working fine, I have DNS Relay off though even when I had it on I didn't experience any lockups like some people here do. I also manually setup OpenDNS (208.67.222.222 and 208.67.220.220) rather than using that Advanced DNS Service.
My connection is PPPoE based, and the WAN port is set to 100Mbps rather than Auto and I also have Multicast streams enabled. SecureSpot, GuestZone, Wi-Fi Protected Setup, Graphical Authentication, Auto Check Firmware, Dynamic Fragmentation are all disabled.
Not sure if UPnP works though since I don't use it, however it is enabled. Same goes for SharePort.
I think that about covers my general configuration. Again, everything was done in IE6, I haven't changed any settings from any other browser.
Not going to guarantee it'll fix your problems but no harm in trying (assuming you have access to IE6).
EDIT: One more thing, I have the A4 hardware revision.
-
;D DIR-655, only IE6 supported ;D
-
I really can't see how using IE6 instead of IE8 has an effect on the router. Care to explain how this is possible?
-
I really can't see how using IE6 instead of IE8 has an effect on the router. Care to explain how this is possible?
Poor web development? IE6 is by far the least standard compliant browser that's in use, so if D-Link coded according to it, it could explain possible quirks.
-
Haven't had any issues with IE7 and IE8, nor with Chrome or Firefox. So would be urprised if it did make a difference.
-
browsers have nothing to do with it. I've used ie7, 8, mozilla, mozilla beta, safari.
-
browsers have nothing to do with it. I've used ie7, 8, mozilla, mozilla beta, safari.
Well it solved my problem so whatever.
-
It is far, far more likely that the order in which you did things mattered and not what browser. And that means the bug is a really hard-to-reproduce issue, which means it will likely never get fixed. DLink is not unique in problems like this, I think every router has issues with firmware sometimes no matter how good they are. There are just so many permutations of things you can do, it is hard to catch them all.
However, if you reset everything and manually make all your settings, that should always work and it doesn't seem to always work with this router. That should be more of a solvable problem, but it still likely depends on what config you use and even then, the order you do it could matter too.
-
This is why I would expect Dlink to use the forum to have error-struck users specify every detail of their config (router as well as LAN/WAN devices). Especially when you cannot reproduce the issues.
-
I tried your Possible fix to a "T". It seems to have helped the WiFi with less drops and pauses. However Shareport problems still are present. Of course as I posted elsewhere I was able to fix the shareport problem by disabling all other Network devices (Bluetooth, Extra LAN Port..etc) and that resolves the issue. DNS problems still seem present as well.
Thanks for the suggestion I can live with the problems until a fix comes out as long as the wireless for the laptops is not pausing every 45 seconds like it was with every other method I tried.
Thanks,
Armyb77
-
I would not say that disabling everything else is a solution or a resolution to another problem. Disabling functionality of a device to make something else work is NOT a solution. You give DLINK that and they will never fix it.
-
It is far, far more likely that the order in which you did things mattered and not what browser. And that means the bug is a really hard-to-reproduce issue, which means it will likely never get fixed. DLink is not unique in problems like this, I think every router has issues with firmware sometimes no matter how good they are. There are just so many permutations of things you can do, it is hard to catch them all.
Yeah, quite possible I guess. And I can't remember the exact order I did things in anyways.
One thing I didn't mention (edited my first post now), is that I have A4 hardware, which as most of you know has some major design changes so that could be another variable.
-
1.21 runs IE8 smoothly...i dont see y 1.31 wouldnt
-
Browers may only affect the GUI. Only when the javascript engine is really corrupt it may prevent execution of settings. But none of the mainstream browsers suffer from that