pls help correct RT-N66R firmware upgrade 3.0.0.4.380_3831 problems?

[pdoyle]

I'd like to 1.) connect to GUI at 192.168.1.1; and 2.) see the correct SSID for ethernet on the Windows 10 desktop.

All was fine until Yesterday, I flashed firmware upgrade; followed minimalist guide to the letter, but then had trouble connecting to the GUI for hours due to 'IP address has been changed; find new IP and Port to connect'. Asus utility then found the router; but couldn't connect to GUI. Before, I could easily connect to 192.168.1.1. Then, browser warned of invalid certificate; creating exception allowed connection, but the warnings are concerning. Now I find the GUI only at at https://router.asus.com:8443/index.asp and at 192.168.1.1:8081. Also, only 13 devices are connected to internet through ethernet and wireless router; formerly there were about 20 devices connected. Plus, the ethernet connection is listed as the former SSID; which was changed yesterday. I had changed all the SSIDs but kept passwords the same for both bands and Guests. I think that's a problem; tried to edit the registry, but that didn't correct the wrong SSID.
thanks!

 

[wouterv]

I suggest to the following steps:

1. While the router is on: press the reset button for more than 5 seconds.
2. Give the router about 5 minutes to start up again.
3. Power down the router and start it up again.
4. Make a wired network connection to the router.
   
5. Access the router at the default IP address 192.168.1.1 and admin/admin
6. You shall get the router configuration wizard.
7. Manual configure the router again (do NOT load an old configuration backup file).
8. Assign brand new SSIDs for 2.4 GHz and 5 GHz, not ones you have used sofar.
   
9. Delete the wireless connection profiles on the clients and rebuild the wireless connection.

Editting the Windows register to change SSID is not the proper way, step 8 is the safest way.

 

[pdoyle]

I suggest to the following steps:

1. While the router is on: press the reset button for more than 5 seconds.
2. Give the router about 5 minutes to start up again.
3. Power down the router and start it up again.
4. Make a wired network connection to the router.
   
5. Access the router at the default IP address 192.168.1.1 and admin/admin
6. You shall get the router configuration wizard.
7. Manual configure the router again (do NOT load an old configuration backup file).
8. Assign brand new SSIDs for 2.4 GHz and 5 GHz, not ones you have used sofar.
   
9. Delete the wireless connection profiles on the clients and rebuild the wireless connection.

Editting the Windows register to change SSID is not the proper way, step 8 is the safest way.

thank you!
followed above instructions and the router seems to be working. Only concern is that both firefox and explorer browsers on windows 10 won't connect to the router IP of 192.168.1.1
Asus utility Device Discovery shows the correct SSID and IP address but I select Configure, instead of the GUI I see
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-N66R.
To access the settings of RT-N66R, reconnect to the wireless network and use the updated IP address and port number.
Can you advise how I can reach the GUI at 192.168.1.1, instead of currently the only way I've found the GUI is at this address, after I make an exception to the following warning at https://192.168.1.1:8443/index.asp
There is a problem with this website’s security certificate.



The security certificate presented by this website was not issued by a trusted certificate authority.

Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.

We recommend that you close this webpage and do not continue to this website.

Continue to this website (not recommended).

More information

 

[wouterv]

Is it mandory for you to set GUI access to https?
If not, I suggest to leave it default http.

 

[pdoyle]

that setting found at Administrative/System/Authentication; is that still secure if set to HTTP? I misunderstood and thought it had to be set to HTTPS to be secure from outside hackers.

 

[pdoyle]

yes, that has fixed the GUI access concern. thank you!
it is secure, yes? doesn't affect my FTP server or DDNS outside access?
thanks!

 

[wouterv]

The user interface is safe with http as long as you do NOT enable "Enable Web Access from WAN".
FTP is a different story, it is considered unsafe because the user credentials are send un-encrypted, as clear text over the Internet.

 

[pdoyle]

The user interface is safe with http as long as you do NOT enable "Enable Web Access from WAN".
FTP is a different story, it is considered unsafe because the user credentials are send un-encrypted, as clear text over the Internet.

Thanks again; it's working fine now.