Public Time Synchronization Servers

[John Hay]

On Tue, Sep 30, 2003 at 10:45:15AM +0300, Odhiambo Washington wrote:
> * Lachlan <lachlan at fatpanda.net> [20030930 10:11]: wrote:
> > Hello,
> > 
> > 
> > http://www.time.za.net/
> > 
> > The above link might be of use to you.
> 
> 
> It sure did, but still seems I am stuck. I have extracted the Stratum-2
> servers from this site and run a test against them, no luck still. The
> error msg I get is the same:
> 
> 
> root@ /home/wash]
>  2# cat FILE2 
> ntp1.icomtek.csir.co.za
> tock.nml.csir.co.za
> ntp.is.co.za
> igubu.saix.net
> ntp1.webonline.co.za
> ntp-ndf.mweb.co.za
> ntp-nld.mweb.co.za
> 
> 1# for server in `cat FILE2`; do ntpdate $server; done
> 30 Sep 10:42:58 ntpdate[55266]: no server suitable for synchronization found
> 30 Sep 10:43:02 ntpdate[55267]: no server suitable for synchronization found
> 30 Sep 10:43:06 ntpdate[55268]: no server suitable for synchronization found
> 30 Sep 10:43:10 ntpdate[55269]: no server suitable for synchronization found
> 30 Sep 10:43:17 ntpdate[55272]: no server suitable for synchronization found
> 30 Sep 10:43:24 ntpdate[55273]: no server suitable for synchronization found
> 30 Sep 10:43:30 ntpdate[55274]: no server suitable for synchronization found
> 
> 
> Is there something that I could be ignoring (since this is my 1st go at
> setting up a Time Server) that is blatantly obvious? For one I know (connectionwsie)
> that SA may not be the closest to me, but surely their Time Servers should
> serve me well ;)

They should. I run the icomtek ones and they don't block anyone... yet. :-)
South Africa might not be optimum for you though because I guess that most
African countries don't peer with each other, so everything have to go
through USA. :-(

> I am still at a loss as to why I get the message.

Maybe there is some kind of firewalling on your side? NTP use udp port 123.

John
-- 
John Hay -- John.Hay at icomtek.csir.co.za / jhay at FreeBSD.org