Cannot get NTP working

Status
Not open for further replies.
Joined
Nov 24, 2013
Messages
214
Hi,

When I try to use the NTP I got this error:

Server could not be reached. Check "Force" to continue regardless.

I check "Force" but the time was not updated.

I found posts on this forum about this issue but it date from 2012.

Thanks,

Guillaume
 

Alvin

Explorer
Joined
Aug 12, 2013
Messages
65
I remember having that error too, and ignoring it.
Try ntpq -p. It should tell you whether ntp is connected to any peers or not.
 
Joined
Nov 24, 2013
Messages
214
This gave me this:

[root@server ~]# ntpq -p
No association ID's returned

This is a good thing?
 

Alvin

Explorer
Joined
Aug 12, 2013
Messages
65
No. You should see a list of peers and their status.
Do you allow 123/udp in your firewall and can you resolve the NTP servers?
 

Alvin

Explorer
Joined
Aug 12, 2013
Messages
65
Did you mean I need to open the port 123 in my ISP router?
Not incoming, but outgoing should be open. Traffic is probably not blocked when you have an ISP router. If you open incoming, your FreeNAS server will act as an NTP server to the outside world. With the wrong settings, that can be abused.

What servers are you trying to reach? The defaults should work, but you can choose the ISP's NTP servers if they provide those.
 
Joined
Nov 24, 2013
Messages
214
I put time.nist.gov as time server, I thought the default NTP servers was down so I set another. I don't know if its possible to open outgoing port on my ISP router. I think there was an option only for open incoming ports. Im with Bell Canada...

Also when I try to ping the NTP server I got this:

[root@server ~]# ping time.nist.gov
ping: cannot resolve time.nist.gov: Host name lookup failure
[root@server ~]#

What I should do now?

EDIT:

I can ping the NTP server by his IP adress, so when I click on save, the time is synced, but if I change the time manualy to one hour back, FreeNAS is not re-syncyed the time automaticly.
 
Last edited:

rogerh

Guru
Joined
Apr 18, 2014
Messages
1,111
NTP doesn't correct a time more than a certain amount out, except when booting if set to do so. I'd try setting half a minute out and see if it corrects that. The theory is that if the time appears more than a few minutes out something is badly wrong and needs human intervention for safety.

Edit: it sounds as though something is wrong with your DNS servers on the FreeNAS box.
 
Joined
Nov 24, 2013
Messages
214
It look like it work now, I change the time this morning with the command date and I wait few minutes and the time was synced to the correct time after.
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
Status
Not open for further replies.
Top