The short answer
First distinguish failed discovery from failed access. If a known IP works manually, investigate multicast scope, adapter choice and isolation before changing credentials.
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 the model manual for an ONVIF service switch and any separate ONVIF account. Use the configured service port; do not assume it equals the RTSP port.
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.
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.
What to verify
Inspect the active Windows network profile and the app’s permitted local access. Use a narrowly scoped app exception when needed; keep the firewall enabled.
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.