albertoconti
join:2009-08-02 | reply to bananaman
Re: DIR-655 Problems with websites, slow loading and finally 404
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? |
|
Fireblade
join:2008-08-27
St Catharines, ON
 ·Cogeco Cable
 ·Vonage
| 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. |
|
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. |
|
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. |
|
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. |
|
hatedlink
@clearnet.com
| 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. yes, ty it finally works! |
|
