Hikvision DS-2CD2132-I NTP settings

[scottismyname]

Hi All,

I have a DS-2CD2132-I that is on the V5.2.0 build 140721 firmware. I have 6 other cameras (DS-2CD2032-I) that are on V5.3.0 build 150327). I am using direct-to-disk in Blue Iris so I cannot use BI to overlay the time, so I have all of my cameras doing the overlay instead. The 6 cameras that are on 5.3 are fine using time.windows.com with NTP updates, however the one on 5.2 will not update. It just keeps saying it cannot connect to the ntp server when I try to test it. I am weary of upgrading the firmware but not sure what else I can try at this point. Anyone else have a good solution to keep all of the times in sync?

 

[aster1x]

Choose other NTP servers and verify if it is a problem of some servers or in case of all servers failing then you either have a faulty firmware configuration or an incompatibility in your network routing. In the latter case connect the camera to another network and repeat tests.

 

[alastairstevenson]

It sounds like the network configuration is not quite working right.
First - check the default gateway is configured as the IP address of your router.
Then check that the DNS server is the IP address of your router, and if not, set it, reboot, and test the NTP setting - if that older firmware has a test button.

If you can telnet or SSH into the 5.2.0 camera, you can check your internet settings at the command line.
First - ping an site by IP address:
ping 8.8.8.8
and see if you get a reply. Control-C to return.
Then ping a site by name:
ping www.google.com
and see if you get a reply. Control-C to return.
If neither of these works, check your camera can ping your router IP address, for example:
ping 192.168.1.1
Then change your DNS setting in the camera to use 8.8.8.8 and re-test

 

[fenderman]

I think you will find that @alastairstevenson advice will solve you problem.
You might also consider running a local timeserver on the machine http://www.timesynctool.com/ I use this with my BI systems. Make sure to let port 123 through the windows firewall (udp)

 

[scottismyname]

Thank you all for the replies.

I tried @alastairstevenson advice, but it did not work. I was able to ping my router and my BI machine, but I still could not ping the outside world.

I ended up running an NTP server on my BI machine and that is working well. Thanks again!

 

[alastairstevenson]

but I still could not ping the outside world.

Well that's strange. I must admit, I didn't spend any time exploring the 5.2.0 firmware, but I'm surprised it can't reach the internet, that's pretty basic Linux functionality.
If you are still curious (despite the fix), you could try these commands (firmware 5.2.3):

login as: root
[EMAIL="root@192.168.254.12's"]root@192.168.254.12's[/EMAIL] password:

BusyBox v1.19.3 (2014-07-11 11:25:54 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       tcp  --  anywhere             anywhere             tcp dpt:telnet
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.254.0   *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 wlan0
224.0.0.0       *               240.0.0.0       U     0      0        0 eth0
default         192.168.254.1   0.0.0.0         UG    0      0        0 eth0
# ping [URL="http://www.google.com/"]www.google.com[/URL]
PING [URL="http://www.google.com/"]www.google.com[/URL] (216.58.210.36): 56 data bytes
64 bytes from 216.58.210.36: seq=0 ttl=55 time=35.479 ms
64 bytes from 216.58.210.36: seq=1 ttl=55 time=27.506 ms
64 bytes from 216.58.210.36: seq=2 ttl=55 time=23.502 ms
^C
--- [URL="http://www.google.com/"]www.google.com[/URL] ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 23.502/28.829/35.479 ms
#