The short answer
Multiple adapters can send camera traffic along an unintended route. Establish which interface reaches the camera subnet before troubleshooting discovery or playback.
Work through the checks
Read the camera address in your router’s DHCP client list or the manufacturer’s local setup tool. Confirm the entry against the MAC address instead of guessing an address.
Check which Ethernet, Wi-Fi or VPN adapter owns the route to the camera. Test a single known route before changing adapter priority or network policy.
Put the computer and camera on a network that permits local communication. A guest SSID, client isolation or a separate recorder PoE network can block access even when both devices have internet.
Test only the configured device and service port from the Windows computer. A successful TCP connection proves reachability to that port, not correct credentials or a decoded video image.
What to verify
Run local ONVIF discovery on the intended adapter. Discovery may not cross routed networks; compare the discovered address with a manual connection to the known camera IP.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.