cannot Synchronize with NTP RLC-410
I recently installed two RLC-410 cameras. NTP synchronization is not working. I get I am getting emails, remote view currently works. I am getting an error: "Failed. Failed to verify configuration."
All of my computers on this network sync with various NTP servers.
I am on the latest firmware build 17061501.
Ideas? Would be very awesome to have all my cameras on the same time...
I'm not sure which NTP server you are trying to sync your time, but if that NTP server is a Linux system, you need to make sure it's NTP config file is configured to allow your IPC camera IP address to query to it.
Here's my snippet of my Linux's /etc/ntp.conf, my IPC camera addresses are in 192.168.x.x:
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
# Enable this if you want statistics to be logged.
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
# Specify one or more NTP servers.
# Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
# on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
# more information.
pool 0.ubuntu.pool.ntp.org iburst
pool 1.ubuntu.pool.ntp.org iburst
pool 2.ubuntu.pool.ntp.org iburst
pool 3.ubuntu.pool.ntp.org iburst
# Use Ubuntu's ntp server as a fallback.
# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.
# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
# Local users may interrogate the ntp server more closely.
# Needed for adding pool entries
restrict source notrap nomodify noquery
# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust
restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap
# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
Hi and thank you for the reply. I'm actually just syncing to standard public NTP servers, such as time.nist.gov. I don't have any of my internal linux boxes serving NTP. I suppose I could set one up to be an internal NTP server and then have the RLC-410 try to connect to that. If it does, then perhaps it's a firewall/route issue.
the time.nist.gov might not be the closest NTP server to your region.
So, it would be good to find the closest NTP server.
Alternatively, like you said, set up one internal NTP server and connect all your IPC to it.
unfortunately, it appears that the camera will not connect to a local network NTP server either. I actually have a standalone NTP server that works with my other devices on the network. The RLC-410 can't get to that IP either.
Also, the time.nist.gov servers work well with the rest of my equipment behind the same router/firewall. The only thing I can see is that there's an issue with the RLC-410 NTP setup.
This is weird, I own an RLC-410 as well and I don't face this problem.
Could you tell us what firmware you using on this IPC?
I have two of them. I've tried syncing them to NTP via the REO link desktop app and the web interface. no luck.
I'm monitoring my firewall for traffic.
The only thing different about these two cameras than everything else on my network is that they're going through a POE+ network switch. Nothing else is on that switch besides a BlueIris Server.
Well, high possibility that your POE+ switch is a way to configure it to join your other network?