The short answer
A Windows network profile controls firewall behavior, not camera credentials. Choose a profile appropriate for the trusted network and verify only the access the app needs.
Work through the checks
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.
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.
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.
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.