NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6400
when trying to acess modem config after reset ....page says must connect to wifi to be able to?
I had tried all solutions you mentioned as I had done extensive research on internet.. In the end as I said the only thing that would work was only connect thru wifi with a naked router. Couldn't use ethernet connection to naked router....I try to run a secure setup so my default browser was highly configured that was why I tried browsers that I don't use... to no avail....in the end it was my default browser that connected to gui just with out internet/modem connected. Probably no one else well have identical problem but our discussion may help someone hopefully.
reset the router with the hardware button.
- On the back of your router, locate the Restore Factory Settings or Reset button.
- Using a paper clip or similar object, press and hold the Restore Factory Settings or Reset button for about seven seconds.
- Release the Restore Factory Settings or Reset button and wait for your router to reboot.
After your router is finished with the factory reset, the Power light stops blinking and lights solid green.
Note: The Power light on newer router models lights solid white.
The factory default settings are restored.
After that, reinstall firmware and reset/erase through gui
> [...] been there done all that.
Been where? Done all what?
If your web browser is going to that misleading/useless error page,
then your problem is more likely a DNS (or URL) problem than it is a
firmware problem. But without a useful description of what you're
doing and seeing, it'll be tough to guess a solution.
Hey appreciate the input....just thought someone else may have had a similar situation.....in the end I had to disconnect the router from the modem and laptop.....factory reset it and connected to the router wirelessly to set it up. Could not do this if it was connected to the modem or laptop with ethernet. I believe it is accessible now and be reconfigured. I am sure I am not as competent as some on this board, but expected the router to behave better after factory reset....never had these issues originally.
After factory resetting initially and connecting to modem it would bring up error even when going to 192.168.1.1....cleared browser caches, tried different browsers to no avail. Most would just get another router but I am persistent believing the router was most likely fine. TWT.
> [...] expected the router to behave better after factory
> reset....never had these issues originally.As already explained, getting to that misleading/useless error page is
generally not a router problem, but a computer/device (DNS)
configuration problem. Accordingly, resetting the router generally
won't change it. Reconfiguring the DNS settings on the computer/device
(so that it uses the router for DNS instead of some outside-world DNS
server) generally will.Yes that was the obvious solution, but it would give that error with using 192.168.1.1....why would I need a DNS server then?
> [...] but it would give that error with using 192.168.1.1.... [...]
That sounds (to me) like a web browser cache problem. If you thrash
around with multiple browsers, different URLs (name, address), and I
don't know what else, then it can be easy to get lost.For a true test, start with a clean browser, connect the router to
only one computer (not to the Internet), and see what happens. Ideally,
that one computer should be set to use DHCP for everything, including
the DNS server.If you complicate the system (different DNS server, Internet
connection, too-clever browser, ...), then whole new vistas of potential
problems open up before you.I had tried all solutions you mentioned as I had done extensive research on internet.. In the end as I said the only thing that would work was only connect thru wifi with a naked router. Couldn't use ethernet connection to naked router....I try to run a secure setup so my default browser was highly configured that was why I tried browsers that I don't use... to no avail....in the end it was my default browser that connected to gui just with out internet/modem connected. Probably no one else well have identical problem but our discussion may help someone hopefully.