This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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.
have tried all methods...i.e. reboot everthing...use different browser...clear cache..etc. same error Can connect to internet, just cant access router management.
Hi, the modem is a netgear cm500. Everything was fine till I tried to push WPS button to connect a printer....the router forgot its SSID...so I factory reset it. now it all works with default password....but when trying to access router to change SSid etc. I get message
You are not connected to your Router’s WiFi network. To access routerlogin.net, your device must be connected to your Router’s WiFi network. Check your current connection and try again. it doesnt matter whether im hardwired or connected by wifi.
Briefly, the idea is that "[www.]routerlogin.net" (or ".com") should point to your own router, but that's true only if you use your own router for DNS name resolution. Regardless, you should be able to get to the thing using its IP address, if you can determine (or guess) that. Normally, that would be something like "192.168.1.1", but it could be different.
Visit http://netgear.com/support , put in your (actual) model number, and look for Documentation. Get the User Manual. Read.
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
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.
> [...] 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.
