I am using an Amcrest NV1104E and 3 cameras all PoE connected.
2 cameras are Foscam, and 1 is Amcrest IP2M-842EB.
If I connect all 3 cams to the built in PoE on the NVR, the 2 Foscam cams get a DHCP address from my LAN(10.0.0.x), but the Amcrest doesn't--instead, it gets 2 listings: LAN IP of the builtin PoE switch (10.0.1.x) on the tcp port 88 AND the ONVIF settings of Port 1 (even though its in port 4) with tcp port 37777. Not such a big deal, in setup I just save the appropriate settings for cameras and channels. The Foscam cams don't update to correct time over the network via NTP, and every 3-7 days, the Amcrest camera magically assigns itself a new IP on the PoE switch (10.0.1.z).
While attached to the PoE switch, routing obviously doesn't happen between the LAN port and the PoE as I cannot connect to the cameras without wiring into the PoE and accessing accordingly that way.
IF I use a regular PoE switch on my network, everything works as it should via the LAN (10.0.0.x) and if I attach it to the built in PoE the symptoms duplicate.
It would be nice if the builtin PoE would route within itself, get appropriate info from its LAN connection for NTP, etc instead of DHCP to keep the overhead cam traffic segmented on the NVR and its switch.
Am I asking too much?
I don't mind contacting support, but wanted to post this in the even it helps anyone else having this problem.
LAN oddities NVR and cams
Re: LAN oddities NVR and cams
I think I figured it all out. Will give it a couple days now to see if it stays.
I found that even though updating IP's through the GUI or the IP tool, rebooting the NVR in between and testing made the difference.
The roving IP was due to a check box setting on the Amcrest cam "allow ping/arp for network configuration"
I also found that before disabling this setting, my camera settings kept wanting to fill in the 4th camera with this other magical IP.
Rebooting the NVR, doesn't retain the correct time stamp on the 2 Foscam cameras, but I wired in an AP so I can at least sync to my computer periodically.
Might try bridging the AP in a couple days to try making it a gateway for the NTP time sync, but at least I got the traffic confined to the PoE builtin switch and off my normal network.
I found that even though updating IP's through the GUI or the IP tool, rebooting the NVR in between and testing made the difference.
The roving IP was due to a check box setting on the Amcrest cam "allow ping/arp for network configuration"
I also found that before disabling this setting, my camera settings kept wanting to fill in the 4th camera with this other magical IP.
Rebooting the NVR, doesn't retain the correct time stamp on the 2 Foscam cameras, but I wired in an AP so I can at least sync to my computer periodically.
Might try bridging the AP in a couple days to try making it a gateway for the NTP time sync, but at least I got the traffic confined to the PoE builtin switch and off my normal network.