hatedlink
@clearnet.com
| reply to Fireblade
Re: DIR-655 Problems with websites, slow loading and finally 404
said by Fireblade  :It's a DNS Relay issue, try this. I disabled DNS Relay, got my DNS servers from my ISP and threw them into my TCP/IP settings in Network Connections. Then, in Network Settings, I Revoked all the IPs and restarted the computers. You have to Revoke the IP's or you'll continue having the problems even with DNS Relay off. yes, ty it finally works! |
|
Fireblade
join:2008-08-27
St Catharines, ON
 ·Cogeco Cable
 ·Vonage
1 edit | reply to alphad
Dude, you've got a screwed up network with 5+ different network devices and you wonder why shit isn't working right?
said by tirebiter :A "404" error originates with the web server that you are attempting to access and has little to do with your router. It's the server telling you that file requested cannot be found on the server. Unless your router is modifying the name of the page you are requesting, it's unlikely that a 404 error can be blamed on your router. The 404 is the router, I had the same thing happen to me with DNS Relay enabled.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
tipstir
join:2004-11-14
Enfield, CT
·Cox HSI
| reply to Fireblade
said by Fireblade :It's a DNS Relay issue, try this. I disabled DNS Relay, got my DNS servers from my ISP and threw them into my TCP/IP settings in Network Connections. Then, in Network Settings, I Revoked all the IPs and restarted the computers. You have to Revoke the IP's or you'll continue having the problems even with DNS Relay off. Can't do that and keep the wireless stable. Right now I have to DNS Relay is enabled. |
|
tirebiter
join:2002-02-16
Champaign, IL
·Comcast
| reply to alphad
A "404" error originates with the web server that you are attempting to access and has little to do with your router. It's the server telling you that file requested cannot be found on the server. Unless your router is modifying the name of the page you are requesting, it's unlikely that a 404 error can be blamed on your router. |
|
Fireblade
join:2008-08-27
St Catharines, ON
·Cogeco Cable
·Vonage
| reply to albertoconti
It's a DNS Relay issue, try this.
I disabled DNS Relay, got my DNS servers from my ISP and threw them into my TCP/IP settings in Network Connections.
Then, in Network Settings, I Revoked all the IPs and restarted the computers. You have to Revoke the IP's or you'll continue having the problems even with DNS Relay off.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
albertoconti
join:2009-08-02 | reply to bananaman
I have the same issue with firmware 1.31. I am getting ready to return the unit. My old netgear g worked better! sad.
Any ideas on what the problem is and how to solve it? |
|
Tsume
join:2004-02-23
Johnson City, TN
 ·Embarq
·ViaTalk
·Comcast
| reply to alphad
said by alphad :I am having the exact same problem as this post » forums.dlink.com/index.php?PHPSE···c=5150.0. I have been updating my DIR-655 A2 with firmware 1.31. However I still have some serious problems... After a few days, pages started to load slowly all of a sudden, after that images and website layout are gone (and only text is displayed) and after that I get 404's... I already tried 30/30/30 (clearing nvram) several times, redid all my settings manually, disabled QOS and stuff... Same issue with DNS relay off, but it takes a lot longer to crop up with DNS relay off.
--
"Did you know that when one little panda pulls on another little panda's underwear, that's sexual harassment? That makes me a sa-a-a-a-ad panda." --Sexual Harassment Panda |
|
Fireblade
join:2008-08-27
St Catharines, ON | reply to alphad
Then you're fine, just turn it off. |
|
gsm1
join:2009-03-10
Renton, WA | reply to gsm1
I am using dhcp. |
|
Fireblade
join:2008-08-27
St Catharines, ON
·Cogeco Cable
·Vonage
| reply to gsm1
Setup -> Network Settings, should see "Enable DNS Relay".
If you turn it off, make sure you either a) run an automatic network connection or b) if you're running a manual connection, make sure you have your ISP's DNS filled in at the bottom, one is enough.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
gsm1
join:2009-03-10
Renton, WA | reply to alphad
This might be a dumb question but how do I turn off DNS relay. I can't seem to find it any where I may have simply over looked it |
|
bananaman
join:2002-10-26
New York, NY | reply to wollja
Just an update on my 1.31NA install: Since disabling DNS Relay it has been up continuously for 26 days and counting, no freezing. Before I disabled DNS Relay it froze every few days. |
|
wollja
join:2009-07-05
Bellingham, WA
| reply to jeremy01
I also upgraded to version 1.31 NA from 1.21 and shortly after had constant problems. At least once every 24 hours I had to manually reboot my router, our computers could not get Internet or Internal network access to each other. All of my computers and devices are wireless b, g & n with no wired connections. I couldn't even get to my routers IP address, a router reboot would fix it for about 24 hours before it would act up again. This never happened with 1.21, which for me at least was quite stable with only a few very minor issues I had hoped the 1.31 would fix.
After tinkering with a whole bunch of settings myself without success, I luckily found this forum and realized I never should have upgraded since they don't allow downgrades on this version and you guys were reporting bugs. I was feeling quite screwed.
Then I found the alphad77 and jeremy01's post, thank you!! I can verify as well that none of the other suggestions worked. For me the only thing that worked was disabling DNS Relay. After disabling DNS Relay and restarting the router though, none of my machines or devices could get back on the Internet but then I renewed my IP leases on all of my machines (Ipconfig /renew) and they all started working.
Since disabling DNS Relay my router has been up for 7 days now and has been rock solid on 1.31NA finally!!! Thanks guys, I don't have to take my shotgun to this router after all, you just saved me some money and frustration!
And I will not upgrade to the next version until people on this forum say it is safe to do so.
Jack |
|
jeremy01
@sbcglobal.net
| reply to alphad77
said by alphad77 :
seems to be an issue with DNS Relay. Once I turned that feature off, my router has been stable for 8 days and counting.
The DNS Relay bug seems to not have been fixed.
I can confirm this. Mine was rebooting once every 24 hours. I tried several iterations of turning off QOS, port forwarding, wifi auto-channel scan, WPS, etc. Finally, after disabling DNS Relay, I'm up to 6+ days without a reboot. |
|
tipstir
join:2004-11-14
Enfield, CT
·Cox HSI
| reply to Fireblade
said by Fireblade :Disabling DNS Relay bricks my router and the 30/30/30 trick is needed to get it rolling again. Crazy you need DNS Relay disabling it doesn't make sense to users to do. Not a quick fix. |
|
Fireblade
join:2008-08-27
St Catharines, ON | reply to alphad
Disabling DNS Relay bricks my router and the 30/30/30 trick is needed to get it rolling again.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
tipstir
join:2004-11-14
Enfield, CT
·Cox HSI
1 edit | reply to Scree
said by Scree :Good thought actually, but no, nothing set up in forwarding at all (nor opened via upnp, I checked that list). There are other "listen" connections like that from other computers on the network, but the computer in question gets turned off and this rogue connection won't leave the list. But anyway, I decided to reboot the router to use the isp dns servers again instead of OpenDNS just to test them out now that comcast raised the speeds here again. So currently at 16 hours uptime. This is either the firmware/Atheros WNPU causing the bug. By disabling the wireless and using 1.30NA with another Wireless Access Point N the problem is'nt there. Nope now TEW-652BRP with DIR-615 C2/3.10NA as the issue too so that could be the firmware or WNPU or just could be both.
Might not be the firmware might be the WNPU Atheros. I wonder fit they switch to another brand for WNPU would they have the same issues. |
|
Scree
In the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ
·Comcast
4 edits | reply to dcurrey
Good thought actually, but no, nothing set up in forwarding at all (nor opened via upnp, I checked that list). There are other "listen" connections like that from other computers on the network, but the computer in question gets turned off and this rogue connection won't leave the list.
But anyway, I decided to reboot the router to use the isp dns servers again instead of OpenDNS just to test them out now that comcast raised the speeds here again. So currently at 16 hours uptime. |
|
dcurrey
Premium
join:2004-06-29
·ViaTalk
1 edit | reply to Scree
said by Scree :Update: hmmm At 12 days 19 hours now, I have a "connection" in Internet Sessions (but it's not in WISH Sessions) that's stuck on a 0 time out and won't go away, from a wireless computer currently off the network (turned off). Will wait and see if this condition spreads. Are you sure you don't have any ports forwarded to that ip. I also have a connection that stays open. Looks like its from the cable mode port 68 udp. Think this is for dhcp to function. |
|
Scree
In the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ
·Comcast
4 edits | reply to alphad
You mean the ICMP 3 messages? On further examination they seem to always be my wired computer. For the "cannot create new session" messages when DNS Relay was on, those had both wired and wireless (which is G only here).
I sure hope dlink collects and reviews all this real-world information. lol
(I didn't say dstink now because at least this major problem seems worked-around with dns relay off  )
Update: hmmm At 12 days 19 hours now, I have a "connection" in Internet Sessions (but it's not in WISH Sessions) that's stuck on a 0 time out and won't go away, from a wireless computer currently off the network (turned off). Will wait and see if this condition spreads. |
|
