OC200 Omada Cloud Controller Inaccessible
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.OC200 Omada Cloud Controller Inaccessible
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi
I have an OC200 which was working okay via cloud and direct from the browser, setup two EAP245 APs and everything was working fine for a couple of weeks. We then had a power outage and when everything came back up the OC200 would not connect to the cloud (so inaccessible from the app or TP website) and going directly via the browser either returns the message "could not connect" or the OC200 starts to load, gets to about 55% and then disconnects with the message "could not connect" or "this page isn't working". I can then only get the OC200 webpage to try to load again if I physically disconnect and reconnect but then it only loads to 50% again.
The OC200 is currently on DHCP but have also tried on fixed IP. It's PoE via a Zyxel GS1900-HP and that's plugged into a Draytek 2860. I can successfully ping the IP from both the switch and router.
The EAP245's are working fine. I've tried a second OC200 with the same problem.
The OC200 is version 3.0.4 with firmware version 1.0.3 Build 20181016 Rel.33052
I've got the same setup in a residential enviroment with the same hardware except the router is a BT Hub (UK) and that works perfectly.
Any help appreciated or thoughts on what to try next or where I'm going wrong.
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
The latest version of the firmware will be released these days, you can download it from the TP-Link offical website by then, this firmware will fix some bugs and add some new function, just upgrade it and check if the problem still exists.
- Copy Link
- Report Inappropriate Content
i think it is not a firmware issue as his oc200 couldnt even bootup completely..
all the issue happened after the electric shortage.. I guess either your poe switch's power module or the oc200 is damage.
you can try powering the oc200 via a qualified DC adapter. if it works then it is the poe switch to blame.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Looks like a firmware issure. Just bought a new OC200 and plugged it in. I set it up successfully and EAPs on the network are all good. I performed the firmware upgrade and the OC200 now doesnt connect to the cloud or even retrieve an IP from my router.
I tried powering it from two different PoE's and via USB (5v @ 2.1A) still not luck.
I tried pressing the reset button and still nothing.
I opened a ticket but my guess is the firmware bricked the OC200 as the router dosent see it on the network.
Keep everyone posted.
- Copy Link
- Report Inappropriate Content
Finally got it working with tech supports help.
The solution that worked for me was to unplug the OC200 from the router and connect it directly to my computer. I set my computer IP to 192.168.0.100, set the subnet mask as 255.255.255.0, set the Default Gateway as 192.168.0.253. This guide may help you https://www.tp-link.com/us/support/faq/14/
I disabled my Firewall and opened my web browser and type in the default gateway address of the OC200, 192.168.0.253. I should have been able to get the login screen but it didnt work so I removed power from the OC200 and held down the reset button while plugging it back in. THis put the OC200 in recovery mode and I was able to load fresh Firmware that I downloaded from TP-Link's wedsite. After the firmware update, I removed power and connected the OC200 back into my router. I waited 2 minutes and the cloud LED finaly started to flash and I proceeded to setup a new controller.
If you are lucky enough to be able to access the OC200 web management page, login with admin / admin and enable the Cloud Access, then put in your TP-Link ID again to test.
- Copy Link
- Report Inappropriate Content
@Marcobio We have the same problem, after I upgrade dated 12/24/2019 I have try this atleast two different OC200 the result is the same. The cloud is not blinking or cannot connect to internet. Have you solve your problem?
Marcobio wrote
Looks like a firmware issure. Just bought a new OC200 and plugged it in. I set it up successfully and EAPs on the network are all good. I performed the firmware upgrade and the OC200 now doesnt connect to the cloud or even retrieve an IP from my router.
I tried powering it from two different PoE's and via USB (5v @ 2.1A) still not luck.
I tried pressing the reset button and still nothing.
I opened a ticket but my guess is the firmware bricked the OC200 as the router dosent see it on the network.
Keep everyone posted.
- Copy Link
- Report Inappropriate Content
@meon Buying a new one is not the answer, for me. I just click upgrade then the cloud not acessable. IS t hat ok i we all click upgrade if not working buy again are you loosing your mind.
- Copy Link
- Report Inappropriate Content
meon wrote
IS t hat ok i we all click upgrade if not working buy again are you loosing your mind.
You don't need to buy a new one. OC200 is a business-class device which has lifetime warranty, so as a last resort you can RMA it if it's really broken due to a firmware upgrade.
But before considering to apply for RMA I suggest to check whether you can access the management UI: press the RESET button while powering on the OC200 and keep it pressed for 5-7 seconds. Then set your laptop to a static IP from the 192.168.0.0 network (e.g. to 192.168.0.10) and try to connect to the OC200's default IP 192.168.0.253. If the mgmt UI loads, re-install the config from a backup.
- Copy Link
- Report Inappropriate Content
@R1D2 This is the second OC200(new) after upgrade the result was the same. Can you guide me to do your solutions? I'm wondering why no subnetmask and defaultgateway?
- Copy Link
- Report Inappropriate Content
meon wrote
Can you guide me to do your solutions? I'm wondering why no subnetmask and defaultgateway?
You always need a subnet mask to define an IP. Just leave the subnet mask at the default of 255.255.255.0 to set the IP 192.168.0.10.
A default gateway IP is not needed since there is no gateway if your laptop is connected directly to the OC200 (a direct connection is recommended to avoid DHCP which complicates things further) and no DNS IP setting is needed since you will not use any domain name.
After a factory reset by pressing the OC200's RESET button for 5 seconds start a browser and load http://192.168.0.253/. The mgmt UI will be loaded and allows you to configure the OC200. Specify an admin password, skip all remaining steps in the setup wizard for now and after this initial setup of the admin password the login page appears. Log into the admin account and go to »Controller Settings → Maintenance« to upload the new firmware. Then proceed with setting up the controller.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 12056
Replies: 15
Voters 0
No one has voted for it yet.