NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
mluvw47
Mar 05, 2017Aspirant
R6900 after firmware updated, no internet connection after doing checking firmware updated again
I updated my R6900 router to the latest verison ( R6900, Version 1.0.1.16) After that, the router get rebooted and I am able to get internet connection and the connected device working fine. Then ...
- Mar 14, 2017
mluvw47 wrote:
Not sure about ISP block anything like that I am aware of it, since it is In my case, I can do manual down the zip and perform update without any issue.:cathappy:
Comcast used to do DNS redirects, but I am not sure they are doing them now.
You can test it by reconfiguring your router temporarily to use 8.8.8.8 as the DNS server (instead of the comcast-supplied DNS). That's google's DNS server.
mluvw47
Mar 14, 2017Aspirant
Not sure about ISP block anything like that I am aware of it, since it is In my case, I can do manual down the zip and perform update without any issue.:cathappy:
IMHO, Just hope that it got resolve and provide a better error message on the page for troubleshooting, so no one will be victim in this matter. :manhappy: Thanks michaelkenward and schumaku
StephenB
Mar 14, 2017Guru - Experienced User
mluvw47 wrote:
Not sure about ISP block anything like that I am aware of it, since it is In my case, I can do manual down the zip and perform update without any issue.:cathappy:
Comcast used to do DNS redirects, but I am not sure they are doing them now.
You can test it by reconfiguring your router temporarily to use 8.8.8.8 as the DNS server (instead of the comcast-supplied DNS). That's google's DNS server.
- michaelkenwardMar 15, 2017Guru - Experienced User
Does this mean that there are DNS out there that don't find the address for the Netgear servers?
- schumakuMar 15, 2017Guru - Experienced User
michaelkenward wrote:Does this mean that there are DNS out there that don't find the address for the Netgear servers?
Yes. I does mean that some ISP are morons and prohibiting or capturing some domains (beyond of certain pssible legal requirements) becuse the "think" these are insecure or whatever. Popular free and commercial dynamic DNS domains (some vendor specific ones, too) for example are caught. And because these and most consumer ISP don't understand that an Internet connection is used for more than Web browsing and with some luck to handle email, M2M communication is torpedized - becuase machines can't read some redirection Web pages, and deal with it accordingly.
Regards,
-Kurt