Trouble with accessing my router

[ThinkWithPortals]

I was having trouble with my router. Before, when navigating to 192.168.1.1 I would get this:

 

"Settings have been updated. Web page will now refresh.
Changes have been made to the IP address or port number. You will now be disconnected from RT-AC68U.
To access the settings of RT-AC68U, reconnect to the wireless network and use the updated IP address and port number."

 

So I decided to reset it (ASUS RT-AC68U) by powering off, holding down the reset button, powering on again. However, when I try to access the router's GUI to set up a login, establish WiFi network passwords, etc. through navigating to 192.168.1.1, I just get "192.168.1.1 took too long to respond." So right now I'm stuck with a router on factory default settings, two open WiFi networks, and no way to access my router's GUI.

 

...help?

[samcool55]

Try 192.168.0.1

[ThinkWithPortals]

Just now, samcool55 said:

Try 192.168.0.1

Takes me to my modem's GUI.

[samcool55]

2 minutes ago, ThinkWithPortals said:

Takes me to my modem's GUI.

Disconnect everything form the network, every device, every router, everything, including the modem.

Plug in the modem and wait until it's 100% operational, after that plug in the router, wait again until that's 100% operational.

Then connect the device you want to use to connect to the router. Just make sure NOTHING ELSE connects to the wifi or wired or whatever.

If everything is done right your device should have the IP 192.168.0.3 and if you try to connect to 192.168.0.2 you should connect to the router.

If the IP of your device is not 192.168.0.3, let us know what it is then. Depending what the IP is we can figure out if something else did connect accidentally or something else went wrong.

 

Again, it's very important to disconnect everything and connect the modem, router and end-device in the right order and nothing else.

[ThinkWithPortals]

2 hours ago, samcool55 said:

Disconnect everything form the network, every device, every router, everything, including the modem.

Plug in the modem and wait until it's 100% operational, after that plug in the router, wait again until that's 100% operational.

Then connect the device you want to use to connect to the router. Just make sure NOTHING ELSE connects to the wifi or wired or whatever.

If everything is done right your device should have the IP 192.168.0.3 and if you try to connect to 192.168.0.2 you should connect to the router.

If the IP of your device is not 192.168.0.3, let us know what it is then. Depending what the IP is we can figure out if something else did connect accidentally or something else went wrong.

 

Again, it's very important to disconnect everything and connect the modem, router and end-device in the right order and nothing else.

This sounds like a great idea. Unfortunately my router had other plans.

 

After a few power cycles and resets I actually got through to the GUI. When I logged in, it started performing a firmware update, which was very explicit in stating "please do not turn off your router or computer during this process". Should be fine, I guess, I'll just let this update proceed.

 

My computer chose this crucial moment to BSOD for the first time ever.

 

Literally the one time where I couldn't afford to lose power unexpectedly and it did. So, as is often the case with a fucked-up firmware update, my router seems to be completely bricked. Yaaaaaay.

 

Thanks for the help, anyway

[samcool55]

18 hours ago, ThinkWithPortals said:

This sounds like a great idea. Unfortunately my router had other plans.

 

After a few power cycles and resets I actually got through to the GUI. When I logged in, it started performing a firmware update, which was very explicit in stating "please do not turn off your router or computer during this process". Should be fine, I guess, I'll just let this update proceed.

 

My computer chose this crucial moment to BSOD for the first time ever.

 

Literally the one time where I couldn't afford to lose power unexpectedly and it did. So, as is often the case with a fucked-up firmware update, my router seems to be completely bricked. Yaaaaaay.

 

Thanks for the help, anyway

Well, that sucks. I guess you can try to botch in a serial connector and hook it up to your pc to flash a new firmware, sometimes that's an option.