Windows SDN Controller 5.0.29 - After upgrade all devices show DISCONNECTED
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I upgraded the Omada Software this morning to 5.0.29. After restart, all devices (2x EAP225v3, ER605) show as disconnected.
Troubleshooting steps taken:
Restarted Omada controller
Rebooted host windows machine
Restored backup from previous version (5.0.15)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I believe I found the issue. For some reason after the upgrade, Windows detected the network as a new, unrecognized network, and decided to classify it as "public". This turned on some firewall rules that prevented network scanning, etc from that computer (which runs the controller). As soon as I found that and told Windows it was a private network, all the devices came back.
Not sure if the upgrade changed something that caused Windows to detect a network change or it was just coincidental.
Thanks again-
Jason
- Copy Link
- Report Inappropriate Content
I do not know if it is the same but I have found that there are some problems with the new controller. I have updated an earlier bug report here.
https://community.tp-link.com/en/business/forum/topic/508242?replyId=1027878
This is a remote controller, do you have the controller on a remote site or is it local?
- Copy Link
- Report Inappropriate Content
@shberge my controller is on the local network. This is a very simple home setup. Just added the ER605 to replace a netgear router but the two APs have been running for over a year.
- Copy Link
- Report Inappropriate Content
Ok, My router and switch adopt with no issue, but I do a test with different access point and the only that work was EAP225-Outdoor.
I do a downgrade for test on EAP245v3 to 5.0.3 and after downgrade it adopt with no issue. so, but you have also problem with the router so maybe there is more bugs than just access point.
- Copy Link
- Report Inappropriate Content
I believe I found the issue. For some reason after the upgrade, Windows detected the network as a new, unrecognized network, and decided to classify it as "public". This turned on some firewall rules that prevented network scanning, etc from that computer (which runs the controller). As soon as I found that and told Windows it was a private network, all the devices came back.
Not sure if the upgrade changed something that caused Windows to detect a network change or it was just coincidental.
Thanks again-
Jason
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1001
Replies: 4
Voters 0
No one has voted for it yet.