Re: Public Time Synchronization Servers

From: Odhiambo Washington (wash_at_wananchi.com)
Date: 09/30/03

  • Next message: Odhiambo Washington: "Re: Public Time Synchronization Servers"
    Date: Tue, 30 Sep 2003 11:13:19 +0300
    To: freebsd-isp@freebsd.org
    
    

    * John Hay <jhay@icomtek.csir.co.za> [20030930 10:53]: wrote:
    [snip]

    I am happy to be in touch with you!!

    > 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.

    No firewall.

    A test against one of your servers, from a FreeBSD 5.1-RELEASE and from a Redhat
    linux box both give same result, viz:

    [root@ns1 /root]# ntpdate ntp1.icomtek.csir.co.za
    30 Sep 11:07:35 ntpdate[16353]: no server suitable for synchronization found

    [root@ns1 /root]# ntpdate -d ntp1.icomtek.csir.co.za
    30 Sep 11:07:49 ntpdate[16354]: ntpdate 3-5.93e Fri Apr 6 13:16:26 EDT 2001 (1)
    transmit(146.64.24.58)
    transmit(146.64.24.58)
    transmit(146.64.24.58)
    transmit(146.64.24.58)
    transmit(146.64.24.58)
    server 146.64.24.58, port 123
    stratum 0, precision 0, leap 00, trust 000
    refid [0.0.0.0], delay 0.00000, dispersion 64.00000
    transmitted 4, in filter 4
    reference time: 00000000.00000000 Thu, Feb 7 2036 3:28:16.000
    originate timestamp: 00000000.00000000 Thu, Feb 7 2036 3:28:16.000
    transmit timestamp: c3240cb8.fd805000 Tue, Sep 30 2003 11:07:52.990
    filter delay: 0.00000 0.00000 0.00000 0.00000
               0.00000 0.00000 0.00000 0.00000
    filter offset: 0.000000 0.000000 0.000000 0.000000
               0.000000 0.000000 0.000000 0.000000
    delay 0.00000, dispersion 64.00000
    offset 0.000000

    30 Sep 11:07:53 ntpdate[16354]: no server suitable for synchronization found
    [root@ns1 /root]#

    -Wash

    -- 
    Odhiambo Washington   <wash@wananchi.com>  "The box said 'Requires
    Wananchi Online Ltd.  www.wananchi.com      Windows 95, NT, or better,'
    Tel: +254 2 313985-9  +254 2 313922         so I installed FreeBSD."   
    GSM: +254 72 743223   +254 733 744121       This sig is McQ!  :-)
    Over the years, I've developed my sense of deja vu so acutely that now
    I can remember things that *have* happened before ...
    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
    

  • Next message: Odhiambo Washington: "Re: Public Time Synchronization Servers"

    Relevant Pages

    • Re: Problem with time synchronisaton
      ... server is running NTP? ... refid, delay 0.05562, dispersion 0.00015 ... offset -0.004013 ...
      (comp.protocols.time.ntp)
    • Re: Public Time Synchronization Servers
      ... > Presumably you did try one at a time and not just the scripting to ... 30 Sep 11:07:35 ntpdate: no server suitable for synchronization found ... refid, delay 0.00000, dispersion 64.00000 ...
      (freebsd-isp)
    • Re: ntp-server broken on dapper?
      ... Here's two examples - one a working ntpd server the other one not... ... Looking for host 192.168.1.2 and service ntp ... refid, delay 0.02574, dispersion 0.00000 ...
      (Ubuntu)
    • Re: Can sychronize with a slightyly different NTP versios
      ... this moment) unit that was serving its own time starts asking for time ... to a PC or a reliable server, the whole network will be in sync. ... refid, delay 0.02623, dispersion 0.00000 ...
      (comp.protocols.time.ntp)
    • mail()
      ... php forum probably has to do with authentication ... Windows 2003 Server? ... Cosmic Link ... South Africa ...
      (alt.php)