The short answer
Discovery can fail across a router while a permitted direct IP connection still works. Diagnose discovery traffic and media routing as separate paths.
Work through the checks
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.
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.
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
For a routed private connection, verify the VPN route to the camera subnet and its access rules. A private route is separate from any AeoCam cloud service; public port forwarding is not required for this check.
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.