IPC-T2431T-AS stays off after a power outage

[d5775927]

I have a Dahua NVR with two IP cameras, each IPC is connected directly to the NVR using a Cat 5e cable (using the NVR to power the cameras).
One of the camera usually doesn't start after a power outage, I can only see it after I reboot the NVR.
To be more clear, if I have a power outage and the NVR shuts down, on the next NVR boot, I only see 1 camera out of 2.

IPC: IPC-T2431T-AS
NVR: NVR4108-8P-4KS2

Any idea of how to make the camera start automatically after power outage?

 

[garycrist]

Does the "bad cam" have static or DHCP set in the network section of the camera?

 

[d5775927]

Does the "bad cam" have static or DHCP set in the network section of the camera?

no.
This is the network config of the two cameras, left side is the bad one:

 

[TonyR]

In both cams:
Where did the IP's for IP Address, Default Gateway, Preferred DNS and Alternate DNS come from?

 

[Flintstone61]

If a guy is using an NVR, as I recall from @bigredfish ,,,,you usually setup NVR cams with DHCP addresses?

 

[d5775927]

In both cams:
Where did the IP's for IP Address, Default Gateway, Preferred DNS and Alternate DNS come from?

I think i've set that, since I don't have a vlan for the cameras.
Adding some more config pictures (I pointed the preferred DNS for the NVR to an IP address which is not in use 192.168.100.253 in my LAN).

 

[bigredfish]

I’ll check but I think if you use the PoE ports on a new camera, it will assign the 10.1.1.x address as static as shown

 

[TonyR]

I must admit that I don't use a NVR but am a Blue Iris VMS on a PC sort of guy but....
I've set up 3 or 4 NVR's for clients, one being an Amcrest (a re-branded Dahua) POE NVR and as I recall the cams were set to DHCP and one-at-a-time plugged into the POE NVR. The NVR in turn would assign unique IP's to the cams on a different subnet as the NVR's LAN. That was a method, I presume, to isolate the cams from the Internet. The NVR's LAN IP was 192.168.1.XXX and the cams were on 10.0.0.XXX. One could then work with the NVR's Gateway IP and DNS IP's to keep it off the Internet as well.

 

[Damon]

If the problem persists try a reset on the bad camera and configure it fresh

 

[TonyR]

+1^^.
I'd do both cams, one cam at a time, let the NVR assign IP's, and if you want, change NVR's gateway and DNS IP's to keep the cams off the Internet; I'd leave the cam IP's alone and let the NVR handle the isolation.

 

[d5775927]

+1^^.
I'd do both cams, one cam at a time, let the NVR assign IP's, and if you want, change NVR's gateway and DNS IP's to keep the cams off the Internet; I'd leave the cam IP's alone and let the NVR handle the isolation.

Thanks, will try.

 

[d5775927]

I've tried to reset the bad camera,but it didn't solve the issue, however, I didn't reset the good camera (since it takes a me a while to restore the settings manually).
I checked this by unplugging the NVR power cord and plugging it back.

 

[TonyR]

I've tried to reset the bad camera,but it didn't solve the issue, however, I didn't reset the good camera (since it takes a me a while to restore the settings manually).
I checked this by unplugging the NVR power cord and plugging it back.

After resetting the "bad" cam, did you try to power it up with a 12VDC wall wart, then with IE11 log into it at 192.168.1.108 and change it from static to DHCP and then save it?
To log into that cam's subnet after a reset, you'd need to be on a PC set static to 192.168.1.XXX (XXX= 1 to 254 but not 108), with a subnet mask of 255.255.255.0, then plug PC's Ethernet port directly into cam.

If you're able to log into it and change to DHCP, then power the cam OFF and plug into NVR's POE port.

 

[SpacemanSpiff]

Swap Ethernet ports used by the problem camera, and another cam that does not exhibit the issue to determine if it is a physical port issue with the NVR

 

[d5775927]

After resetting the "bad" cam, did you try to power it up with a 12VDC wall wart, then with IE11 log into it at 192.168.1.108 and change it from static to DHCP and then save it?
To log into that cam's subnet after a reset, you'd need to be on a PC set static to 192.168.1.XXX (XXX= 1 to 254 but not 108), with a subnet mask of 255.255.255.0, then plug PC's Ethernet port directly into cam.

If you're able to log into it and change to DHCP, then power the cam OFF and plug into NVR's POE port.

No, I didn't try this. I reset the camera connected it to the NVR and then reconfigured mostly as it was before (without changing network related stuff).

 

[d5775927]

Swap Ethernet ports used by the problem camera, and another cam that does not exhibit the issue to determine if it is a physical port issue with the NVR

Sound like a good idea (that I should have tried first), will try this.

 

[d5775927]

Sound like a good idea (that I should have tried first), will try this.

Tried to switch Ethernet ports, got the same result, the bad IPC doesn't boot.

 

[Flintstone61]

Must be a fault in Camera if Nvr designated IP addressing is being allowed run in default settings. Unless somebody changed some ip addressing scheme inside the camera gui.

 

[d5775927]

Must be a fault in Camera if Nvr designated IP addressing is being allowed run in default settings. Unless somebody changed some ip addressing scheme inside the camera gui.

I've reset the IPC today didn't change any IP related settings.

 

[SpacemanSpiff]

Tried to switch Ethernet ports, got the same result, the bad IPC doesn't boot.

Do you have a power injector or a PoE switch to do some additional diagnostics?

It still under warr?