-
September 7th, 2016, 02:48 PM
#1
Can't Log In to Router/Switch
Hi, I have a T-Mobile provided TM-AC1900 router (they call it the Personal Cellspot which is actually a rebranded Asus RT-AC68U router) being used as a switch and WiFi Hotspot. It is hooked up to the Verizon FIOS MoCA router (LAN to LAN, and with the DHCP turned off in the Asus).
I have set this up many times before and it is working just fine. Except that, since two days ago I haven't been able to log in the Asus's admin page. The browser (Chrome. IE, Firefox, doesn't matter) says the page can't be reached. I triple checked the IP address (which is 192.168.29.1) and I even use the Asus "Device Discovery Tool" to find the Asus's IP and it confirms that 192.168.29.1 is correct.
I just can't understand why I can't log in. I have certainly logged in before, many, many times, without any issue. I have changed nothing since I logged in last time.
Please help me figuring this one out.
-
September 7th, 2016, 03:31 PM
#2
Did you try restarting and/or resetting the router? If restarting doesn't help, then you probably need to factory reset the router and redo your settings.
-
September 7th, 2016, 04:44 PM
#3
BTW, did you try connecting directly to the router via cable?
-
September 7th, 2016, 06:02 PM
#4
Originally Posted by Midknyte
Did you try restarting and/or resetting the router?
Originally Posted by Midknyte
BTW, did you try connecting directly to the router via cable?
Yes and Yes.
-
September 7th, 2016, 06:10 PM
#5
-
September 7th, 2016, 08:28 PM
#6
Originally Posted by Midknyte
No. Actually, I thought you meant "power cycle" which I had done to avail. Factory reset I haven't doesn't done yet but I will try it when I have the time to deal with it. Just don't understand how it functions fine otherwise except this problem all at a sudden.
-
September 7th, 2016, 08:39 PM
#7
Restart = power cycle, Reset = Factory Reset. I mentioned both. Hard to say what the cause is, but a factory reset would be the next logical step.
-
September 8th, 2016, 01:03 AM
#8
Funny thing is, I can't even ping the IP address of the Asus (it'd time out). Yet, the switching and Wifi function are still working. Wierd.
-
September 8th, 2016, 01:30 AM
#9
What is your FIOS IP range? 192.168.29.1 is not a typical router IP. More common subnets would be 192.168.0.x or 192.168.1.x.
If you can't ping 192.168.29.1, then how is the Asus "Device Discovery Tool" detecting it?
Did you try setting your wired connection to a static IP like 192.168.29.2? If your IP is not in the same subnet, it probably won't be able to see the router.
-
September 8th, 2016, 02:26 AM
#10
From what I've read, the default FIOS subnet is 192.168.1.x. If that's the case, you should change the Asus router IP to 192.168.1.2 (or another number within the subnet, but outside the DHCP scope).
Like I mentioned before, set a static IP on your NIC and connect directly to the Asus router. See if you can hit the config page that way.
-
September 8th, 2016, 11:55 AM
#11
The 192.168.29.1 isn't the IP address for the FIOS MoCA router (which is the internet gateway). The MoCA's IP is 192.168.1.1.
The WiFi radio in the MoCA router isn't that good, so, like many FIOS users, I use another router (in this case the TM-AC1900) as a WiFi hotspot. The Asus is hooked up to the MoCA LAN to LAN. The MoCA is the only one doing DHCP (DHCP is turned off in the Asus). The default IP for this T-Mobile rebranded Asus is 192.168.29.1 and it is within the MoCA's subnet range (I checked when I first set it up).
Yes, it is strange that I can't ping the IP but yet the Asus Device Discovery Utility tool is able to find it (I've run the tool many times just so I can confirm it.)
-
September 8th, 2016, 01:16 PM
#12
The default IP for this T-Mobile rebranded Asus is 192.168.29.1 and it is within the MoCA's subnet range (I checked when I first set it up).
No, it's not. The MOCA is in the 192.168.1.x network, and the Asus is in the 192.168.29.x network. Like I mentioned before, you should change the Asus router's IP to something like 192.168.1.2 or 192.168.1.250.
http://www.ezlan.net/router_AP.html
-
September 12th, 2016, 12:29 PM
#13
You are correct. I don't know what I was thinking. I used to put the the "secondary" switch/wifi hotspot in 192.168.1.169. I have replaced it a few times and this is a replacement TM-AC1900 T-Mobile gave me (the first one broke after a year). Evidently I forgot to change the IP when I set it up.
Anyway, I did a factory reset and I was able to login. Change its IP to 192.168.1.169. Setup everything and it's fine.
Thanks.
Still I don't understand why couldn't I login before even when I had only the Asus directly wired to PC.
-
September 12th, 2016, 03:03 PM
#14
Still I don't understand why couldn't I login before even when I had only the Asus directly wired to PC.
Did you set a static IP on your NIC? If not, DHCP from the MOCA router would have given you a 192.168.1.x address, not 192.168.29.x.
After the reset, the ASUS had DHCP re-enabled, so your PC would have picked up a 192.168.29.x address.
-
September 17th, 2016, 08:59 AM
#15
Originally Posted by Midknyte
Did you set a static IP on your NIC? If not, DHCP from the MOCA router would have given you a 192.168.1.x address, not 192.168.29.x.
After the reset, the ASUS had DHCP re-enabled, so your PC would have picked up a 192.168.29.x address.
Ah, that makes sense. Thanks for the explanation.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|