Omada OC200 controller doesn't see a particular wired Win10 client PC
I am setting up an Omada based home network, which is currently connected as follows:
- TL-SG2210MP switch
- Incoming ISP fiber router (DHCP server)
- OC200 controller
- Wired Win10 client A
- EAP-225 Outdoor
- Long outdoor cable to opposite corner of house to a generic Netgear gigabit unmanaged switch
- Wired Win10 client B
There are around 40 mixed wireless clients (laptops, phones, smart devices & bulbs etc) connected across the three EAPs & as far as I can tell everything in the house is showing up as a client in the management console as expected. The only thing that doesn't show up in the console is the Win10 client connected to the unmanaged switch upstairs. The EAP-225 is there, as are all the wireless devices connected to it, but the wired PC doesn't show up at all.
I've tried the usual unplugging & replugging into different ports, power cycling etc. The OC200 and SG2210MP are on their latest firmware. The PC itself is working perfectly well, and does show up as an active client on the DHCP list of the fiber router as an active device. (edit: it's set up as DHCP with no manual DNS settings or anything else, just default Win10 DHCP settings)
One of the main reasons for setting all this up is to stabilise the network for gaming to not be interefered with by active downloads and streaming across the ever-growing wireless clients. Typically the one PC that's not showing up is the one that suffers with latency issues when others in the house are streaming etc. I'm wating for delivery of a TL-R605 to complete the rest of the config.
The only explanation I can think of is that the issue is something to do with going through the unmanaged switch. I can't plug the PC directly into the cable from the SG2210MP at the moment, as it won't reach the PC in another room. Is there anything else I could be missing here, or has anyone else seen a similar problem?