Moving controller to a new remote location
Hello,
After having setup the OC200 controller at home, and ensured all was working, I moved it to the final customer remote location, with another network and even another provider.
At home, during the setup and testing, I used a single EAP110-Outdoor. In the remote location I have 3 other EAP110-Outdoor; currently working and setup as single AP and not in a Omada environment. The EAP that I used at home was not moved to the new location and it is currently still at home.
I was expecting that, as soon as I plugged in the OC200 in the remote location, from the "https://omada.tplinkcloud.com/#controller" I could start seeing the OC200 and I would be able to set it up with the other remaining EAP's.
Instead the controller does not come ONLINE and remains forever OFFLINE.
I have plugged-in one of the EAP100 directly into the controller second eth port, to ensure signal was flowing though the controller and that it was properly connected to the Internet. The EAP is working fine, proving that the controller is rightly connected to the network and to the Internet.
I have also tried to access it via the APP on my Smartphone, while the Smartphone was connected within the network where the controller currently is located, but the controller stays offline all the same.
Does this mean that the controller must stay within the original network where it was originally setup, and can never be moved to a new location ?
If this was true, what happened if the Internet provider changed the public IP ?
Or worst, what happened if the customer changed provider ?
Or, simply, did I do something not quite correct ?
Thank you for helping, if you can.