NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 firmware update then intermittent "Hmm, we're having trouble finding that site"
Installed firmware 1.0.9.34 into R7000. No problems with that.
Since upgrading firmware however have encountered web site error "Hmm, we're having trouble loading that site".
This appears on PC m...
Hi again IrvSp
It was during our exchange I was able to get the IPv4 DNS mapped to Google (was something like 10.0.0.1 prior). It looks now like there's no problem connecting to any of the test sites I've tried.
Where I'm located suspect bandwidth is shared amongst the local community so will repeat the bash test during business hours to stress connectivity. Fingers cross that goes well.
Appreciate you pointing in the right direction.
J
IPv4 is the Google DNS's... they should work.
IPv6, you actually using it? Very very few sites really require it? Try disabling IPv6 as a test... that phone hotspot probably does do IPv6 either.
Hi again IrvSp
It was during our exchange I was able to get the IPv4 DNS mapped to Google (was something like 10.0.0.1 prior). It looks now like there's no problem connecting to any of the test sites I've tried.
Where I'm located suspect bandwidth is shared amongst the local community so will repeat the bash test during business hours to stress connectivity. Fingers cross that goes well.
Appreciate you pointing in the right direction.
J
I'm having the same problem and already had IPv6 disabled. I've tried changing DNS servers and even bypassing the router for DNS. The problem persists. I don't recall having this problem when I first updated the firmware. Now it is happening all the time. Kinda smells of an active exploit.
Sorry to hear you're having problems even after changing DNS.
I'm happy to report no occurence after disabling IPv6 and chaning all DNS settings to 8.8.8.8 with alternate 8.8.4.4. (Had to do this for both 2.4GHs and 5GHz channels.)
Will also advise, for some reason when I keyed in a DNS change it didn't always 'take' as evidenced by' ipconfig /all'. Ended up confirming each change - after that no prob.Good luck.
Jonslee wrote:
Sorry to hear you're having problems even after changing DNS.
I'm happy to report no occurence after disabling IPv6 and chaning all DNS settings to 8.8.8.8 with alternate 8.8.4.4. (Had to do this for both 2.4GHs and 5GHz channels.)
Will also advise, for some reason when I keyed in a DNS change it didn't always 'take' as evidenced by' ipconfig /all'. Ended up confirming each change - after that no prob.Good luck.
Glad you got it working. Just a couple of things. One any IP address starting with 10. is a private address and not available on the Internet so would never work for DNS other then a local server.
I assume when you did the ipconfig /all you had done a ipconfig /release and then a ipconfig /renew. Just doing an ipconfig /all shows current but if changes were made not be reflected unless the client was restarted.
