Omada Software Controller (Windows 11) - missing Wifi and Wired clients on the clients list - 5.9.31
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I recently migrated my Omada Software Controller from an older Windows PC with 8GB of RAM to a new Windows 11 PC with 32GB of RAM, both Omada controllers were running v5.9.31 at the time of migration, same version on both. I've noticed that certain clients are not "seen" by the new software controller. The new Windows 11 PC does sit behind a dummy switch (but so did the older Win 11 PC), but other than that it is directly wired to my LAN and has full network access and no local firewall rules that would restrict it from seeing certain network clients. I am using a 3rd-party OPNsense router/firewall as my gateway, instead of an Omada device, though that didn't seem to have an impact on what the previous Windows 11 Omada software controller could see on my LAN.
For example, the new Omada controller doesn't see my Nest Doorbell camera, which is on a Guest network SSID. It is nowhere to be found on my clients list, even though it is accessible and clearly joined to one of my Omada EAPs. The previous Windows 11 Omada Software Controller, same version, 5.9.31, could see that device in addition to a few others that the new controller does not appear to see on the network. Is there any way to force the software controller to "re-discover" these clients on my network? Or should I expect them to eventually show up at some point? Both wired and wireless clients are definitely missing from the clients list...there are about 60 clients on my LAN, both wired and wireless, the new Omada controller (after migration) only sees about 50 of these clients now.
I've followed all of the tips found here - https://www.tp-link.com/no/support/faq/2980/ - however, this did not resolve my issue. Java is permitted through the Windows firewall, and there are no topology restrictions, such as the Omada software controller being on a different subnet or VLAN. As I mentioned previously, the Windows 11 PC running the Omada SDN has access to every device on the LAN, same as the previous Windows 11 software controller.
Note that this issue is about seeing clients (wired and wireless) on my network, NOT devices, such as EAPs. The new Windows 11 Omada Software controller provisioned and adopted every "device" (EAP and Omada switch) without a problem.
I've noticed that a lot of MAC addresses are showing up in the "NAME" column for Known clients, instead of the custom names I've given the clients. However, a lot of the names are still showing up as well. The Nest cam does show up in Insights...when I click the "Forget" icon to the right, a "General Error" pops up. I haven't rebooted the Nest camera, but I've connected to it and had it disconnect/re-join the network. The Nest cam is functioning just fine on the network, it's just not showing up in the clients list. I also see a lot of duplicates showing up in Insights, but when I try to "Forget" any of them, I just get a "General Error." I've posted a screenshot...is there a way to rebuild and/or reconcile the clients list?
*** Note that this topic was covered in another thread. TP-Link support seems to have found the issue and a fix should be upcoming.
