DS-2CD2132-I & DS-2CD2032-I reboot problem

[Buggah]

For about a year now I have a DS-2CD2132-i up and running without a problem, but a couple of month abo it started to reboot itself without a clear cause. Sometimes it's doing it for an hour straight and then it starts recording again like nothing ever happened. I returned it to the vendor. He put it online for 5 days straight, no problem. When I got it back again, same problem. This has been going on for months now.

As of today I got myself a DS-2CD2032-I, guess what: reboots randomly, as a matter of fact they both start rebooting at about the same time.

I'm lost....

Any ideas would be very welcome.

 

[fenderman]

Welcome to the forum. How are you powering these cameras? have you tested it on a short known good cable?

 

[Buggah]

Hi,

Both are powered with different POE devices but the problem also occured they I power it with a power supply. I've tested the DS-2CD2132-i with a shorter cable. Same result.
I think it's something in the LAN that gives a "reboot" signal.

 

[fenderman]

Hi,

Both are powered with different POE devices but the problem also occured they I power it with a power supply. I've tested the DS-2CD2132-i with a shorter cable. Same result.
I think it's something in the LAN that gives a "reboot" signal.

You can test this by connecting directly to a pc and see if it happens..
Is there an NVR involved here? how are you recording? Is there an ip address conflict?

 

[Buggah]

Both cams are on dedicated ips 192.168.1.233 and 192.168.1.234. No other device is the range above .230
One is recording to a Windows share, the other one is connected to a POE switch only. Not recording

What you mean by "directly to a pc"?

 

[fenderman]

you can either plug the camera directly to a pc and power via 12v or connect only the pc and camera to switch (no router or anything else connected)..
In the network settings change the ipv4 settings from auto to (in your case) 192.168.1.200 you will be able to log into the camera at its static ip address of 192.168.1.233 or 234..this way you isolate network issues...make sure to change ipv4 back to auto or your wont be able to go online

 

[Buggah]

Ok, i'm doing that now for one of them

 

[Buggah]

These are the things I did;
- Connected 1 directly to the POE switch and a pc -> no problem
- checked the logs for the other camera from this night and also from a number of night ago -> no problem

Now I noticed that everytime I started checking for problems I always use one specific laptop and as soon as I turn that laptop on and it connects to the LAN, both cams reboot at the same time. When I keep the laptop connected the the LAN, the cams keep rebooting every now and than, as soon as I shut it off, the problem is solved. I have no clue but the laptop seems to be doing something on the lan that make the cams reboot.

I'm just wondering if there is a certain network broadcast that is able to cash a hikvision cam

 

[Buggah]

I made a 4 wireshark files from the second I switch on my wireless adapter on my laptop and both CAM crash immediately. (tried it 4 times) If there is a network specialist in the house, I can post the files

 

[alastairstevenson]

I'd be interested in having a look - I've done a fair bit of poring over network captures in my time. Presumably the files were taken on the offending laptop. How large are they?

 

[Buggah]

I put them in a rar file http://buggah.com/ipcam/captures.rar (730kb)

Some network stats for you:
192.168.1.1 modem/wifi (fritzbox 7490)
192.168.1.3 second wifi ap (linksys)
192.168.1.10 PC (24/7 up, Cam1 uses this PC to write to a share (SMB))
192.168.1.233 Cam1 (static)
192.168.1.234 Cam2 (static)
192.168.1.50 - 192.168.1.200 DHCP for iphone,ipad and laptops

files 1-3 laptop is on DHCP
files 4,5 laptop was given static ip 192.168.1.222

In file 1 on record 357 you see a cam ARP on the network.

Let me know if you need longer files

 

[alastairstevenson]

OK, got them. Not promising anything - but will be interesting to look.

 

[Buggah]

I made an even longer capture:

file 6: http://buggah.com/ipcam/file6.rar


- Laptop is on dhcp, Wifi did not connect right away. First DHCP request from laptop is on 126
- At the same time I have ping 192.168.1.233 -t running
- record 531 ARP request is done for 192.168.1.233
- record 1131 and 1132 both cams have rebooted and Broadcast ARP 192.0.0.64
(DS-2CD2032,192.168.1.234, MAC: C0:56:E3:A2:7F:8B DS-2CD2132, 192.168.1.233, MAC 44:19:B7:30:B3:00)
- If you see: 192.168.1.15 it's a Marantz reciever (static ip)

Thanks for looking!

 

[alastairstevenson]

Your link isn't quite right for file6 - but I got it anyway, thanks for the supporting info.

I've had a look through the other files.
Presumably there is going to be a specific pattern of network activity that causes a panic or fail in the IP processing on the cameras, a bug, and triggers the reboot. But exactly when that happens is invisible in the captures from the laptop, the cameras don't figure in the traffic. So I was puzzling how to hook on to that point in time within the camera, and then to correlate it with the laptop network activity. But no easy ideas sprang to mind. Not even trying to tie the camera recording traffic stopping in.
Looking at the captures - nothing particularly unusual, except a passing thought that the laptop is doing quite a lot of ARP, about itself as well, and the fritzbox is a bit slow to get back to it.

Presumably the cameras have the same firmware version? I wonder if there is any scope to sidestep the issue if Hikvision have changed or fixed anything relevant.
Can you connect the laptop via a cable and do you get the same effect on the cameras?

 

[alastairstevenson]

The longer capture file6 is quite interesting in that the last ping pretty well shows when the camera stops operating - and the laptop has been fairly quite on the network prior to that. I hadn't thought a ping would repeat fast enough to be a useful marker - but in fact it is, in your capture.
But I see no clue as to specific cause. It has to be a fairly subtle bug in the camera firmware.

 

[alastairstevenson]

OK, so I had a look through the various captures.
Only on File1 and File6 does the capture span the initial part of the camera boot process where it ARP tests if the IP address 192.0.0.128 - possible TFTP upgrade server - is available.
With an estimated 2-3 seconds from boot start to that ARP, based on your useful File6 with the continuous ping, that narrows down the time period to look for candidate offending traffic.
In both File1 (frame 352) and File6 (frame 1118) we have the laptop doing a multicast DNS response just before the camera reboot.
It might be interesting to do some more captures and see if that pattern persists.

I'm not sure if multicast DNS is an integral part of Windows 7 etc (is the laptop running Vista?), but it's certainly a core part of Apple's networking, in Bonjour, which would be installed alongside iTunes and Quicktime etc.
It might be interesting as an experiment to check if you have the Bonjour service running, and to set it as disabled.

 

[Buggah]

Hi Alastair,


Thank you for taking the time to look into it. This laptop is running Windows 7 pro and yes it has Bonjour service enabled. I've disabled it now and rebooted the machine. At this point
It looks like you are right, at least for one of the cams (192.168.1.233), the other one still reboots. If you look at http://buggah.com/ipcam/poging12.rar the live stream of 192.168.1.234 freezes around frame 350 - 450.

If you look at http://buggah.com/ipcam/poging13.rar you see a direct connection capture. Only the laptop and 192.168.1.234 are connected to the POE switch. Now 192.168.1.234 stays up and running.

Well at least one of them is not crashing anymore it seems

 

[Buggah]

:mad-new: I just started another Windows 7 PC and both cams rebooted :mad-new:
I totally confused.

 

[alastairstevenson]

Well that's a bit odd. Doesn't make much sense - though it does seem like something has changed by no longer having the multicast DNS packets from Bonjour.
On your File12 - .234 reboots somewhere within frames 732-750 while the laptop is talking to an Apple server.
My conclusion is that Apple has a thing about Hikvision cameras. Or is it the other way around??
Just kidding.
But to get back to the camera firmware - what's the version on each camera? Just wondering if there is scope for a speculative upgrade. Though that isn't without its pitfalls, as this forum amply demonstrates.

*Edit File12, not File10 *

 

[Buggah]

Both cams have;

Firmware V5.2.0 build 140721Code V5.0 build 140714

--
This week i'm going to do some more testing, i'm going to take a laptop from work which has never been in my LAN and see what happens.
I'm thinking more and more that it's some kind of broadcast done by a router of switch.