The short answer
A private VPN can provide a network path to a camera when routes and permissions allow it. This is network configuration, not an AeoCam cloud-viewing feature.
Work through the checks
Write down the exact outcome you need: live observation, a saved event, camera movement or long-term retention. Check each outcome separately instead of treating a visible stream as proof of all functions.
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.
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.
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
Test one camera and one stream before opening a larger camera wall. Keep the camera settings unchanged while you establish whether the first live image is stable.
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.