Thanks
@Teken for your response. I will set it to DHCP this evening as the NVR sits at a friend’s home.
If the issue comes back I will put it back to the factory default settings because a MAC reservation did not yet have any effect so far. The ISP router did not reboot and yet lost connection with the NVR.
Putting it out of the DHCP pool also didn’t work so far. I will update in +/- 72 hours because that’s the timeframe it usually loses it’s address
For the benefit of others who may be asking or running into similar problems. I am going to call out some of the things you noted was done in post 1.
But, is
NOT Industry Best Practices . . .
The target device will be either assigned a Static IP Address, Assigned a DHCP Leased Address, or Reserved IP Address based on MAC. You do NOT assign a Static IP Address anywhere else besides the target device or from the Firewall / Router / DHCP Server.
This must be done only in a single location / service . . .
You do NOT run more than a single DHCP Server unless you know what you're doing and it serves a specific edge case. Such as another isolated network that provides specific services etc. Outside of the NVR being hard coded which is extremely hard to believe.
Any device that is acting strange should always be factory reset to a good known state. Doing so will remove configuration conflicts / errors. Sometimes you may have to reflash the firmware or upgrade the same to resolve a corrupted system or to fix an unknown bug.
The reason you reboot the device more than once is many devices will install the firmware. But, won't fully load everything that was asked of it. Rebooting the target device several times will quickly mimic a request to release the IP Address and reach out to the DHCP Server for the assigned IP address.
This is a dynamic tests of the entire network infrastructure . . .
A static test would be to allow the reserved IP Address to be accepted by the NVR. Once accepted and assigned whatever it's supposed to be - unplug the Ethernet cable. You will see one of two scenarios where the assigned IP Address will remain the same or it will revert back to whatever the default is.
This is important to note because many network devices have a
Fall Back Address to ensure Joe Public can follow the RTFM because the IP Address is known and is from the User Manual. Most devices have a
Watch Dog timer for different aspects of the system to determine state of health, reachability, and operation.
In the above scenario (IF) the NVR keeps the assigned IP Address. The next step is to reboot the NVR to see what happens and dollars to donuts it will return to the default or assigned address. This is expected because the NVR is set to DHCP and can't obtain a lease / reserved IP Address and thus falls back to the default IP.
Every network device is supposed to follow industry best practices of keeping the assigned address unless its rebooted. Because it also has a lease time before it releases the IP address it was given and this only applies to when its NOT connected to the DHCP Server / Firewall / Router.
