DS-2CD2032-I thoroughly bricked? No tftp, SADP, telnet

[Derrick M]

So, I had 4 gray market cameras and was able to get 3 updated to v5.4.5 using the R0 / DS-2CD2x32 BrickfixV2 tool. However, one camera failed after loading the digicap.dav file for the tool.

Now I cannot connect to the camera at all. When I set my PC (which is connected to the same switch as the camera) to 192.0.0.128 and restart the camera I observe the following:

1. While running tftp I only get to the second line, where it lists the device at 192.0.0.64. It nevers actually connects to the device(3rd line).
2. Wireshark seems to confirm the above. The camera broadcasts a "who is" for 192.0.0.128 from 192.0.0.64, but any further communication seems non-existent.
3. Telnet to 192.0.0.64 does not work.
4. SADP does not find the device.
5. I cannot ping the device at 192.0.0.64
   
6. A hard reset using the button on the back of the camera yields the same results above
7. I also tried changing the PC address to 192.168.1.128 to see if the camera had switched IP addresses to 192.168.1.64, but there was no device found at that address.

So paperweight? Serial connection worth it?

 

[alastairstevenson]

I cannot ping the device at 192.0.0.64

Odd if it's doing the ARP for 192.0.0.128 from 192.0.0.64
But if it's going past the bootloader, that would just be 2 or 3 ping responses after power up.

As a longshot, if it boots past the bootloader, if the watchdog is active, you might just find it in SADP after the 10 minute watchdog timeout.

So paperweight?

No, not if you're curious enough to look in more detail.

Serial connection worth it?

I'd say so, if you want to spend the time.
You can issue various update commands when you access the bootloader which should fix it up.

 

[Derrick M]

I'll try SADP again when I get home. I also need to check the Wireshark logs again, but I also vaguely remember something when I was running Wireshark after setting my PC to 192.168.1.128 that seemed to show something with an IPv6 address broadcasting shortly after I rebooted the device. I only mention it because I think the manufacturer name was the same as when the camera sent the broadcast from 192.0.0.64. However, I don't have IPv6 enabled on my router.

It was late night last night, and I am bit foggy after working on it for 6 hours. I'll report back with screenshots later.

Thanks for taking a look.

 

[Derrick M]

No luck with SADP after letting it sit for 30 minutes. Wireshark screencaps with and without tftp running: Unsee — Free online private photos sharing