Unable to automatically set time

[John Aldrich]

When I attempt to enable the automatic time setting, it will let me get as 
far as setting the NTP server I want to use, but then it comes up and gives 
me an error that it can't contact the NTP server. Any suggestions? I *am* 
behind a DSL router, and if need be, I can put an exception in the firewall 
to allow NTP, but I shouldn't need to as I think it allows anything 
*outbound* and restricts *inbound* connections.

[Patrick O'Callaghan]

On Thu, 2010-04-15 at 22:27 -0400, John Aldrich wrote:
>  When I attempt to enable the automatic time setting, it will let me
> get as 
>  far as setting the NTP server I want to use, but then it comes up and gives 
>  me an error that it can't contact the NTP server. Any suggestions? I *am* 
>  behind a DSL router, and if need be, I can put an exception in the firewall 
>  to allow NTP, but I shouldn't need to as I think it allows anything 
>  *outbound* and restricts *inbound* connections. 
Note that some ISPs restrict access to NTP (strange but true). Does NTP
work from some other machine on your network?

Also, you may need to fix filter rules in your router, not just in
Fedora.

poc

[John Aldrich]

On Fri April 16 2010, Patrick O'Callaghan wrote:
>  
>  Note that some ISPs restrict access to NTP (strange but true). Does NTP
>  work from some other machine on your network?
>  
>  Also, you may need to fix filter rules in your router, not just in
>  Fedora.
>   
Well, I just tried running "ntpdate pool.ntp.org" and got an error that
the 
NTP socket was already in use. Any idea how to see what's using it?

[Patrick O'Callaghan]

On Fri, 2010-04-16 at 14:10 -0400, John Aldrich wrote:
>  On Fri April 16 2010, Patrick O'Callaghan wrote:
>  > 
>  > Note that some ISPs restrict access to NTP (strange but true). Does NTP
>  > work from some other machine on your network?
>  > 
>  > Also, you may need to fix filter rules in your router, not just in
>  > Fedora.
>  > 
>  Well, I just tried running "ntpdate pool.ntp.org" and got an error that the 
>  NTP socket was already in use. Any idea how to see what's using it? 
netstat -A inet|grep :ntp

poc

[John Aldrich]

On Fri April 16 2010, Patrick O'Callaghan wrote:
>  
>  netstat -A inet|grep :ntp
>   
Nothing. Comes back to a blank prompt. :-(

[Patrick O'Callaghan]

On Fri, 2010-04-16 at 21:14 -0400, John Aldrich wrote:
>  On Fri April 16 2010, Patrick O'Callaghan wrote:
>  > 
>  > netstat -A inet|grep :ntp
>  > 
>  Nothing. Comes back to a blank prompt. :-( 
I just tried your test and got the same result. I suspect it means that
the ntpd daemon is already running, which in my case it is, rather than
than that the port is actually busy. You can verify by doing:

pgrep -fl ntpd

Note that ntpdc can be used to query the running daemon (ntpdate is
deprecated and will eventually disappear). Try "ntpdc -p".

poc

[John Aldrich]

On Fri April 16 2010, Patrick O'Callaghan wrote:
>  On Fri, 2010-04-16 at 14:10 -0400, John Aldrich wrote:
>  > On Fri April 16 2010, Patrick O'Callaghan wrote:
>  > > Note that some ISPs restrict access to NTP (strange but true). Does
>  > > NTP work from some other machine on your network?
>  > > 
>  > > Also, you may need to fix filter rules in your router, not just in
>  > > Fedora.
>  > 
>  > Well, I just tried running "ntpdate pool.ntp.org" and got an error
>  > that the NTP socket was already in use. Any idea how to see what's
>  > using it?
>  
>  netstat -A inet|grep :ntp
>   
Interesting. If I use the -u flag for the "unprivileged port" it works.

Hmm...