ASUS headache - Help!

[pmcn]

Now just type in those 3 commands from post #24.

So did that... and it seems to have completely bricked it. Endless cycle of re-booting and unable to access from wired or wireless connection. After a while I tried power cycling it. No change. Hard re-boot with the WPS button pressed. No joy.

I have now gone and re-set my 68U as a router and set that up - which is why I am now back on line, but the 86U seems dead. Completely. Have you any idea why? Or how/if it can be resurrected?

 

[ColinTaylor]

Is this (exactly) what you've tried?

If your router fails to boot due to corrupted/invalid nvram settings, then you will have to turn off the router, press the WPS button (on Asus routers), then turn on the router. Wait about 10 seconds, then release the WPS button.

 

[pmcn]

Is this (exactly) what you've tried?

Yes... I held the WPS button until the power light went out then let go. If I plug the ethernet cable from my computer into one of the ports the relevant light flashes for a while then goes out. It keeps going round that loop, but I can't access it via the GUI.

 

[ColinTaylor]

Try manually configuring your PC's network adapter with an appropriate static IP address (i.e. 192.168.1.10 or 192.168.50.10). See section 2 here.

Then try running continuous pings from two separate command prompts.

ping -t 192.168.1.1

ping -t 192.168.50.1

Now when the router reboots itself does either of the pings get a response?

Try putting the router into Rescue mode: Power off the router, press and hold the reset button, power on the router, wait until the power LED flashes slowly and then release the reset button. See sections 3-1 to 3-3 here. If it goes into Rescue mode try accessing the CFE web interface by its IP address.

 

[pmcn]

Try manually configuring your PC's network adapter with an appropriate static IP address (i.e. 192.168.1.10 or 192.168.50.10). See section 2 here.

Then try running continuous pings from two separate command prompts.

ping -t 192.168.1.1

ping -t 192.168.50.1

Now when the router reboots itself does either of the pings get a response?

Try putting the router into Rescue mode: Power off the router, press and hold the reset button, power on the router, wait until the power LED flashes slowly and then release the reset button. See sections 3-1 to 3-3 here. If it goes into Rescue mode try accessing the CFE web interface by its IP address.

Destination host unreachable from pinging 1.1 and occasionally gets this from pinging 50.1 but more often just times out. No joy in recovery mode - computer times out either with router.asus.com or 192.168.1.1

 

[Grisu]

86U usually has IP 192.168.50.1 while 68U has 192.168.1.1.

 

[ColinTaylor]

Destination host unreachable from pinging 1.1 and occasionally gets this from pinging 50.1 but more often just times out. No joy in recovery mode - computer times out either with router.asus.com or 192.168.1.1

From what I remember the default factory-set IP address for the RT-AC86U is 192.168.50.1. I don't know whether that's true for all models.

Was that (192.168.50.1) the default IP address your router came with? If so that is the address you need to focus on and configure your PC with 192.168.50.10.

Getting into rescue mode can often be fiddly an requires you to release the reset button at the correct moment. If you release it too late the router tries to boot normally.

If you see the router responding to pings with a TTL=100 you know that is when you need to release the reset button.

 

[pmcn]

I think the default ip router address is 192.168.1.1. I have never had a device with 192.168.50.anything, so I am sure it wasn’t this. For recovery mode, the light kept flashing slowly, so I presume it was in recovery mode.

So, what now?

 

[pmcn]

There has been no response to any ping. Either time out or host unreachable

 

[Grisu]

Use two cmd-windows and run 1.1 and 50.1 in the other, most 86U have 50.1, maybe you didnt see it because you used http://router.asus.com in the for login 86U.

 

[ColinTaylor]

For recovery mode, the light kept flashing slowly, so I presume it was in recovery mode.

So, what now?

In rescue mode you should be able to access the router's CFE using http://192.168.50.1 or http://192.168.1.1 (depending on the model) assuming you have manually configured your PC with an IP address within the same subnet (i.e. 192.168.50.10 or 192.168.1.10).

 

[KevTech]

https://www.snbforums.com/threads/rt-ac86u-default-ip-address.44588/

Mine is 192.168.50.1

Are you also setting static IP on the PC?

Rescue mode or the mini web will not work if PC is left on automatically obtain IP.

Need to set it like this then after you are done with rescue mode or miniweb you can set it back to automatic:

 

[pmcn]

In rescue mode you should be able to access the router's CFE using http://192.168.50.1 or http://192.168.1.1 (depending on the model) assuming you have manually configured your PC with an IP address within the same subnet (i.e. 192.168.50.10 or 192.168.1.10).

So, with PC IP address set to 192.168.1.50 I tried to get at 192.168.1.1 and with PC it set to 192.168.50.50 I tried to access 192.168.50.1. The power light is slowly flashing. No joy, just times out.

 

[pmcn]

https://www.snbforums.com/threads/rt-ac86u-default-ip-address.44588/

Mine is 192.168.50.1

Are you also setting static IP on the PC?

Rescue mode or the mini web will not work if PC is left on automatically obtain IP.

Need to set it like this then after you are done with rescue mode or miniweb you can set it back to automatic:

View attachment 21822

Yes, static is like your picture.

 

[ColinTaylor]

So, with PC IP address set to 192.168.1.50 I tried to get at 192.168.1.1 and with PC it set to 192.168.50.50 I tried to access 192.168.50.1. The power light is slowly flashing. No joy, just times out.

On your PC can you post the output of this command:

route print

 

[pmcn]

On your PC can you post the output of this command:

route print

===========================================================================
Interface List
7...fc aa 14 9b 6c 0a ......Intel(R) Ethernet Connection I217-V
1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.50 281
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.1.0 255.255.255.0 On-link 192.168.1.50 281
192.168.1.50 255.255.255.255 On-link 192.168.1.50 281
192.168.1.255 255.255.255.255 On-link 192.168.1.50 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.1.50 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.1.50 281
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.1.1 Default
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
7 281 fe80::/64 On-link
7 281 fe80::84e3:1734:6ddf:2ea5/128
On-link
1 331 ff00::/8 On-link
7 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

 

[pmcn]

On your PC can you post the output of this command:

route print

 

[pmcn]

just looked again at the reset procedure that started all of this - slight typo - don't know if this is the problem (ser instead of set)

 

[ColinTaylor]

just looked again at the reset procedure that started all of this - slight typo - don't know if this is the problem (ser instead of set)

OK that's quite useful actually. Because the "set" command was never accepted in effect you didn't make any changes to your router. You just rebooted it. The PC's default route is also correct.

I'm coming to the conclusion that this must be some kind of hardware issue. Regardless of what firmware version you were using or what changes you may have made you should always be able to access the router in rescue mode.

Clutching at straws... try changing the Ethernet cable between the PC and the router. Try plugging the Ethernet cable into different LAN ports (you are using a LAN port and not the WAN port?).

 

[pmcn]

Am thinking that I am completely useless here. Mistook the LED off button for the WPS button. Now done a proper hard reset and it has come up with the GUI.

I will try again to configure a network with it and post back what happens.

Thanks again to all. Still don’t know why it wouldn’t go to recovery mode... but there we go.