The short answer
Use the ANNKE procedure applicable to the model and firmware. A missing separate-user menu can reflect newer behavior rather than missing ONVIF support.
Work through the checks
Identify the camera by model, hardware revision, firmware and MAC address. Keep this inventory separate from passwords; two devices with similar names may expose different protocols.
Follow the ANNKE instructions for the relevant firmware. Older documented menus create an ONVIF account; the newer behavior described by ANNKE may use the activation account without that menu.
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.
Use the camera’s local protocol account. A cloud app email address is not necessarily a valid RTSP or ONVIF login. Grant only the viewing or control permissions actually needed.
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.