1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

Adding another AC66U_B1 into AiMesh with AC66U_B1 + AC68U Fails

Discussion in 'Routers' started by zunfire, Jan 11, 2019.

  1. zunfire

    zunfire New Around Here

    Joined:
    Jan 11, 2019
    Messages:
    2
    Did setup AiMesh between AC66U_B1 + AC68U in december successful, got another AC66U_B1 now and this one fails completely, refuses to be found as node no matter how I try.

    Have factory reset all routers and try over and over again with different approach but same procedure on both AC66U_B1, but later one fails all the time to be found, have them physical placed next to each other.

    There is one differens and the only one I can found H/W ver.:

    Firmware 3.0.0.4.384_45149 on all

    ASUS RT-AC68U H/W Ver.:E1 Version 3.00.4.384.45149 AiMesh router, works every test.
    ASUS RT-AC66U B1 H/W Ver.:A1 Version 3.00.4.384.45149 AiMesh node, works every test.
    ASUS RT-AC66U B1 H/W Ver.:B2 Version 3.00.4.384.45149 AiMesh node, wont be found as node.

    Can anyone confirm AiMesh success with Ver.:B2 ??
     
    Dr Lorenzo likes this.
  2. rjbu

    rjbu New Around Here

    Joined:
    Dec 28, 2018
    Messages:
    2
    I have 2 RT-AC66U B1 H/W Ver.:B2 Version 3.00.4.384.45149, working fine with
    one as AiMesh router and the other as AiMesh node.
    If you logged into each router individually and updated the firmware to latest,
    double check that the B2 is still set to AiMesh Node mode.

    Bob
     
  3. zunfire

    zunfire New Around Here

    Joined:
    Jan 11, 2019
    Messages:
    2
    Thanks for the response.

    Every router is factory restored (couple of times :/) and updated to 3.00.4.384.45149
    But how do you mean check that B2 is still set to AiMesh node mode?

    When I set any of the AC66U B1 router to AiMesh node either throw ”operation mode” option in “administration” tab or I reset it and chose AiMesh node in wizard router.asus.com it seems they end up in a factory reset state waiting for AiMesh router to find it and connect to it and configure it.

    For me it seems that when you select AiMesh node the routers ends up in factor reset state waiting to be found from AiMesh router, right or wrong?


    Its very odd, doing same procedure on both AC66U B1 and the later one fails all the time to be found from AC68U
     
  4. Dr Lorenzo

    Dr Lorenzo New Around Here

    Joined:
    Yesterday
    Messages:
    1
    Sorry to hijack the thread, but I have exactly the same issue but with a DSL-AC68U as the AIMesh Router and an RT-AC66U_B1 H/W Ver.:B2 as the AIMesh node and it's driving me nuts...

    They both have the latest firmware and I have reset the DSL-AC68U once (pain to get all the settings back) and the AC66U loads of times, using loads of methods (GUI factory restore, GUI initialise, reset button, 30/30/30, WPS button method). The AC68U never finds the AC66U as an AIMesh node; the closest it's come has been to flash up a message saying that it was waiting for the AC66U to be ready...

    ASUS DSL-AC68U - Firmware 3.0.0.4.384_21128 (latest available firmware)
    ASUS RT-AC66U B1 H/W Ver.:B2 Version 3.00.4.384_45149

    I followed the video and the online process, I've run thorugh the wizard in the node GUI to set it up as a node (many times), no joy...

    Called Asus support, who could only really recommend following the online process for setting up AIMesh but suggested resetting the AIMesh router as well as the node :/. The second time they recommended pressing the reset button for five seconds on the node, leaving it to do it's thing, and then immediately searching for the node via the GUI in the router. It didn't work...

    They have now advised that I open a ticket, which I've done, so will feed back if I manage to get anything useful from them.