D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-825 => Topic started by: dugbug on August 20, 2009, 02:16:29 PM
-
Hi,
I have kept up with the latest firmware patches for my RevA 825. But unfortunately every so often it completely dies both over wireless and gig-e. I cannot open 192.168.0.1 and no traffic flows.
Cycling the power on the unit recovers networking.
Anyone else see this? Its getting to be down right frustrating for those non-techies in the house to have to know to "reset the white box in the office" whenever the internet dies.
-d
-
Based upon the frequency of discussion here and on the DSLReports Dlink forum, the need for frequent rebooting is a common issue with DIR-825 version A routers that have been updated to firmware version 1.11 or later. Some have reported the need to do it daily (and sometimes more frequently). My experience is more like yours. Every 3-7 days.
Some report having been able to swap theirs out under warranty for either a Rev B, or a Rev A which ships with firmware v1.01 (which apparently did not have that issue). Others, like me, who don't have that option, are hoping for the next firmware update. Dlink says that it is not possible to roll back v1.11 or later to an earlier version.
Barry
-
The issue is also happening with the 655 with its latest firmware.
Disable "DNS Relay" option on the network page. Then restart your computers(or release/renew the connection) after you save the router setting.
You should be ok after that.
-
Can anyone else comment on "DNS Relay"? I disabled it (per the suggestion above), thinking that there could be cache issues, but I'd be interested in hearing more...
-
Can anyone else comment on "DNS Relay"? I disabled it (per the suggestion above), thinking that there could be cache issues, but I'd be interested in hearing more...
Set aside a little reading time and check this thread out: http://forums.dlink.com/index.php?topic=6641.0
There are many others detailing exactly the same issue/fix with V1.11
Cheers
-
>:(
I upgraded (sidegraded?) to 1.12 thinking it would solve the poor performance and lockup problems with my DIR-825 rev A1 router. No luck. Still hanging every other day or so and needs a reboot to recover. Router also refuses to respond to web requests at its assigned IP (in my case 192.168.1.1 ). Is anyone home at D-Link?
-
Set aside a little reading time and check this thread out: http://forums.dlink.com/index.php?topic=6641.0
There are many others detailing exactly the same issue/fix with V1.11
Cheers
Thanks for the link. I went through the last 3 pages of that thread, and my count is that about 80% of the people who disabled DNS relay either had no improvement or only a moderate increase in the number of days before the router locked up again. A few reported no lockups, but all of those had only gone a couple of days with the new settings before posting (so may not have had enough time to really judge the benefit). I did not go thru and check whether any of those who reported later lockups were people who had reported good results initially.
I have made the change and we'll see the result. Based on the experiences of posters in the referenced thread, my bet would be that problems will continue. Hope not, but trying to be realistic (and patient).
-------------------------------------------
Update...what timing. The router locked up immediately after I disabled DNA relay, rebooted the router, and sent the reply above. Could not even access it via the IP address (which I had been able to do previously). Had to power cycle it. Maybe its just a coincidence and unrelated to disabling DNS relay. Or maybe not. Time will tell.
-
Hello. I've been experiencing this problem ever since I got this device. I just upgraded to Firmware v1.12NA in the hopes that this would solve it, but to no avail.
D-Link --> Get this problem fixed A.S.A.P. or I will purchase another router and throw this DIR-825 in the garbage and you've lost a customer for LIFE. I was planning several other D-Link purchases as I build out my network, but if you can't handle something as simple as this, then I can't trust your products.
-
Hello. I've been experiencing this problem ever since I got this device. I just upgraded to Firmware v1.12NA in the hopes that this would solve it, but to no avail.
D-Link --> Get this problem fixed A.S.A.P. or I will purchase another router and throw this DIR-825 in the garbage and you've lost a customer for LIFE. I was planning several other D-Link purchases as I build out my network, but if you can't handle something as simple as this, then I can't trust your products.
Is this happening with DNS Relay disabled on the Setup/Network page?
-
Is this happening with DNS Relay disabled on the Setup/Network page?
The DNS Relay box is checked and greyed out. I can't uncheck it. From what I've read, this isn't the issue.
-
The DNS Relay box is checked and greyed out. I can't uncheck it. From what I've read, this isn't the issue.
I've never seen a vendor (overtly) participate in their "user forums" much, but as a happy D-Link customer (formerly Linksys...), I'd hate to see you go.
I suggest:
- Create a new thread here, specifying the model, firmware and problem in the subject-line. Something like "Dir-825, v1.12NA: Why constantly re-booting!?"
- Also checking DSL Reports' D-Link Forum: http://www.dslreports.com/forum/dlink (http://www.dslreports.com/forum/dlink)
- While grayed-out, if you do try some more with your 825, I'd still watch the "DNS Relay" issue (just in case). There may be something else causing it to be grayed-out. A device as small as the 825 has too little memory for a real DNS cache. I disabled it on my 2.02NA firmware, but it looks like "DNS Relay" was even a bigger problem on the A1 HW.
-
DNS Relay is checked and grayed out because Advanced DNS Service is ENABLED (checked) under the Internet Connection page.
-
DNS Relay is checked and grayed out because Advanced DNS Service is ENABLED (checked) under the Internet Connection page.
That is correct. I unchecked the one and then I could uncheck the other. However, afterwards my computer could not resolve hostnames for websites and POP email, etc.
-
This is because you have to repair your connection on the PC. Because DNS Relay takes responsibility away from the PC when checked. When unchecked the PC needs to pick up that resposibility. When you repair the connection, the PC will pick up the DNS Server addresses and all will work fine.
Repairing the connection can be done:
1) By right clicking the Local Area Connection icon in the lower right corner (by the clock) and choosing Repair
2) Or, by right clicking Network Places, choosing Properties and then right clicking Local Area Connection and lastly, choosing Repair
3) Or, by opening a command window and typing "ipconfig /release" and then "ipconfig /renew"
When ever you change that option in the router you have to repair your connection locally on each PC connected.
-
This is because you have to repair your connection on the PC. Because DNS Relay takes responsibility away from the PC when checked. When unchecked the PC needs to pick up that resposibility. When you repair the connection, the PC will pick up the DNS Server addresses and all will work fine.
Repairing the connection can be done:
1) By right clicking the Local Area Connection icon in the lower right corner (by the clock) and choosing Repair
2) Or, by right clicking Network Places, choosing Properties and then right clicking Local Area Connection and lastly, choosing Repair
3) Or, by opening a command window and typing "ipconfig /release" and then "ipconfig /renew"
When ever you change that option in the router you have to repair your connection locally on each PC connected.
Yep. I found another thread that discussed this also. I'm back up and running with my Mac seeing the DNS servers of my ISP instead of my router as the DNS server. So, now I guess the question is whether or not this solves the lock-up/need-to-reboot problem. If the lock-up was being caused by the router caching dns and running out of memory, then I would think so. Either way, appreciate your help and I'm sure others are going to benefit from this thread as well.
1knight
-
I've also been having this problem (on A1 hardware) since updating to 1.11. I'm puzzled and disappointed that D-Link has not addressed this yet.
I have disabled DNS Relay for now and will see what that does for me.
-
^ 1.12 has been out since 7/29/2009! A lot of stability issues have been addressed, however some (including myself) do still have some lockups from time to time, but it has been vastly improved from the daily resets that was 1.11.
Disabling DNS relay is still a must however.
-
I have HW:B1, with 2.02NA firmware.
I've only had mine about 1.5 weeks, but once I got it configured, it has stayed-up just fine. I let it run about a week, then shutdown for an incoming thunderstorm.
"DNS Relay" is disabled. I never had it "crash" the router, but the router is too small for a reasonable DNS cache so after I understood what it was, I disabled it.
-
^ 1.12 has been out since 7/29/2009!
Sorry, didn't make myself clear. The problem started for me with 1.11NA but when 1.12 became available I installed that, but to no avail.
-
This started in 1.11 on the 825, and 1.22B05 on the DIR-655. Its def a firmware issue across multiple D-Link products.
I haven't followed this on the 825, but are people seeing the freezing on B1? B1 uses a different platform than the A1 (the A1 is the same as the 655). I wondering if this is a problem related to the Ubicom SDK or something that D-Link did (since the B1 isn't based on Ubicom).
-
^ 1.12 has been out since 7/29/2009! A lot of stability issues have been addressed, however some (including myself) do still have some lockups from time to time, but it has been vastly improved from the daily resets that was 1.11.
Disabling DNS relay is still a must however.
Yeah, about those daily resets, mine still does it by itself. I've tried reconfiguring it but whenever I check the status, its never over 2 days, resets itself before that.
-
I wouldn't mind quite so much if it reset itself, but it just bogs down and eventually stops responding. When this happens I can't even reliably connect to the router to do a reboot and have to manually pull the plug.
-
Yeah, about those daily resets, mine still does it by itself. I've tried reconfiguring it but whenever I check the status, its never over 2 days, resets itself before that.
"Connection Up Time" is not the same as router up time. There is no status for router/system/chassis up time that I could find. You can however view your log to see when it last rebooted.
My connection up time currently says 1day 15 hours, but my router has been up for 4+days.
Anyone still having problems after flashing to 1.12 needs to reset to factory and rebuild the config manually.
-
BOFslime, do you have evidence that rebuilding the configuration manually helps? I'm pretty sure I have done that, to no avail.
-
Rebuilding the config after updating has been stated multiple times by dlink reps as a problem correction step. 1.12 certainly isn't bug free, but I had major issues with my device on 1.11, and 1.12 fixed the majority of those stability problems.
-
I'm sure they recommend that as a standard step for just about any problem - it's not clear to me that it would help this specific problem. I'm willing to give it a try.