NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
After firmware update refuses local browser connect for admin ("192.168.x.1 refused connection")
I have been logging in to administer this router for several years from the local network. Sometimes via local LAN sometimes via WLAN, sometimes via remote into a server I remote into. (Never allowed...
MPotamia wrote:I have been logging in to administer <<snip>> And how do I fix?
===========
I found someone to go in an power reboot the R6300v2. It now gives login prompt, and all
And firmware on router shows V1.0.4.46_10.0.93, not what I said earlier (I couldn't login to see what it said). Also I thought things were working before reboot just not giving login to browser, but i was wrong, DNS was hosed I didn't realize it.
This is the first time an update didn't go right, and required a manual reboot.
Out here / MP
MPotamia wrote:I have been logging in to administer <<snip>> And how do I fix?
===========
I found someone to go in an power reboot the R6300v2. It now gives login prompt, and all
And firmware on router shows V1.0.4.46_10.0.93, not what I said earlier (I couldn't login to see what it said). Also I thought things were working before reboot just not giving login to browser, but i was wrong, DNS was hosed I didn't realize it.
This is the first time an update didn't go right, and required a manual reboot.
Out here / MP
> I found someone to go in [...]
Wow. You can do that? Even when "The router is 4800 miles away
across a big body of water"? Astounding. Did you figure that out all
on your own, or did you need to consult an expert at the Department of
the Bleeding Obvious?
> This is the first time an update didn't go right, and required a
> manual reboot.
I wouldn't depend on it being the last. But now that you've figured
out the primary secret to remote operation, you should be ok.