I have an NV4108E-E with 5 IP5M-T1179EW cameras installed via the POE ports on the NVR. Everything was working fine.
I had to replace my router. I did so and everything is working fine with it and I can view the WebUI of the NVR from my computer. I noticed that only one camera was appearing when I did a Live View.
I went to Management->Camera and saw the cameras listed with a red dot in the Status column at the bottom of the page. I deleted them all from that list and then they appeared in the top section of the page a few seconds later.
I then selected them all and added them to the bottom list again. I then edited each one and updated the password to the known password for each camera (the same one for all). All turned to a green dot and were visible in the UI except for camera channel #1. I double-checked I entered the proper password and it still remained red. I tried deleting it from the list and re-adding it and updating the password several times but it remained red.
I removed that camera's cable and plugged it into an external POE switch to get an IP address on my regular network. I was able to then view the camera's config page in my browser and the camera worked fine. The password was as expected and I could access the configuration pages as well as the live view successfully. The camera works fine.
I plugged it back into the NVR and it was detected fine again, but when I add it to the bottom list of cameras and update the password, it remains with a red status.
I put it back to the external POE switch and did a factory reset using the web UI for the camera and then reconfigured it as I had it before including my usual password. I could view the camera perfectly in the browser UI via a direct IP address. I connected it back to the NVR and re-added it to the list, updating the password as needed. It still remains with a red status.
I called Amcrest support but the tech immediately said "open the camera and do a hard reset". It seemed a bit premature and quick diagnosis given the camera works perfectly via the web UI and is also sensed properly by the NVR. It just can't be viewed via the NVR. Since the camera is installed high on the house, I'm hoping there is some other fix for this that doesn't involve climbing a ladder to disassemble the camera dome and push a button on the inside to reset it.
Any ideas what's going on or how to correct it?
Thanks!
After replacing router, one camera won't add back into NVR
Re: After replacing router, one camera won't add back into NVR
Only 2 things comes to mind
IP conflict
Power Supply Failing
So IP conflict need to make sure that your NVR switch isn't setup for the same IP range as the Front Side (Normal Network side)
Backside AKA NVR Switch normally comes as 10.1.1.1 and hands out 10.1.1.65 as the normal first IP that IP can change to something like 10.1.1.128 if it chooses but you get the point..
Resetting the Camera is the first and easy way out. However in truth the best thing to do is double check your settings..
Using the NVR GUI, Main Menu, Then Network, Then TCP/IP and make sure that your local IP is setup for the IP of your Normal Network for your Router.
Next NVR GUI, Main Menu, Network, Switch. It would normally be 10.1.1.1 and need to make sure it isn't the same as your Front side if it is change that IP is the easiest way to fix it. LIke one of mine is 10.8.23.1 and another is 10.23.8.1 and main NVR is still 10.1.1.1 and while it might not matter I don't like the idea that my main NVR a Amcrest 4216E-AI NVR can use both front and back side IP addressed from the front.. So I left that the same as normal and changed the others even though they don't work both sides..
Outside of that and maybe it is just me. But I would have said try and Reset the NVR and not the camera. Remember the POE NVR is good in a since because unlike a DVR when you Reset the NVR you don't have to do all the setup for the Grids and other changes within the Recorder because all that is stored in the Camera..
When you do a Reset of the DVR you have to not only setup all the Grid Info for Motion but all other things that are driven from the Recorder and not stored in the camera..
Next part isn't for everyone...
For a Complete Reset and setting up new. Personally I would Reset my Cameras to factory (Leaving the admin admin) and then once all them are Reset I would Factory Reset the NVR with all the Channels setup in the NVR where I want them.. Then when you do your NVR Setup, Once you get the Screen thank you for buying our product I would go back to the Users, Change Admin password for a new one and after that change the NVR will ask if you want to Sync with your Cameras and I would say yes. Then your cameras and your NVR are setup with the same password without having to Remote to them to make that change and they will be more secure then keeping them admin admin. I do Reset mine a lot so it is no big deal for me. Others don't like having to factory Reset any device it can be a pain...
IP conflict
Power Supply Failing
So IP conflict need to make sure that your NVR switch isn't setup for the same IP range as the Front Side (Normal Network side)
Backside AKA NVR Switch normally comes as 10.1.1.1 and hands out 10.1.1.65 as the normal first IP that IP can change to something like 10.1.1.128 if it chooses but you get the point..
Resetting the Camera is the first and easy way out. However in truth the best thing to do is double check your settings..
Using the NVR GUI, Main Menu, Then Network, Then TCP/IP and make sure that your local IP is setup for the IP of your Normal Network for your Router.
Next NVR GUI, Main Menu, Network, Switch. It would normally be 10.1.1.1 and need to make sure it isn't the same as your Front side if it is change that IP is the easiest way to fix it. LIke one of mine is 10.8.23.1 and another is 10.23.8.1 and main NVR is still 10.1.1.1 and while it might not matter I don't like the idea that my main NVR a Amcrest 4216E-AI NVR can use both front and back side IP addressed from the front.. So I left that the same as normal and changed the others even though they don't work both sides..
Outside of that and maybe it is just me. But I would have said try and Reset the NVR and not the camera. Remember the POE NVR is good in a since because unlike a DVR when you Reset the NVR you don't have to do all the setup for the Grids and other changes within the Recorder because all that is stored in the Camera..
When you do a Reset of the DVR you have to not only setup all the Grid Info for Motion but all other things that are driven from the Recorder and not stored in the camera..
Next part isn't for everyone...
For a Complete Reset and setting up new. Personally I would Reset my Cameras to factory (Leaving the admin admin) and then once all them are Reset I would Factory Reset the NVR with all the Channels setup in the NVR where I want them.. Then when you do your NVR Setup, Once you get the Screen thank you for buying our product I would go back to the Users, Change Admin password for a new one and after that change the NVR will ask if you want to Sync with your Cameras and I would say yes. Then your cameras and your NVR are setup with the same password without having to Remote to them to make that change and they will be more secure then keeping them admin admin. I do Reset mine a lot so it is no big deal for me. Others don't like having to factory Reset any device it can be a pain...
Be Safe.
Re: After replacing router, one camera won't add back into NVR
Thanks for your reply. I really didn't want to reset the NVR too, so after trying various deletes and re-adds, I finally did a software reset (from the web UI) on the camera again, and re-added it to the NVR list. It showed a red status dot again, so I left it for a while to do some research. After about 5 minutes, I reloaded the ASP program and the camera displayed! I checked the web UI and the dot had turned green. In all other cases, the dot would start red after adding the camera, then after updating the password it would change to green within a couple of seconds, but I watched this one NOT change for several minutes after updating the password each time, so I have no idea what caused it to work this time or why it was so slow to be recognized after being updated.
But anyway, it's working now!
But anyway, it's working now!
