Re: Cannot synchronize to server with local clock

On Wednesday, July 20, 2005 at 9:32:31 PM +0930, Tim wrote:

> I have dial-up internet, so my network is only ever on the net some of
> the time. I had that machine run a local clock, since the machine is
> always running, and used it as the clock server for my LAN (so they
> all stayed in step with each other).

Yes, that's one of the usages of LOCAL(), undisciplined or rarely
disciplined, fudged at a high stratum like 8 or 10.


> If I remember correctly, its stratum changed from 16 when unsynced, to
> one less than the source it uses for synchronising (when in sync with
> it).

The LOCAL() driver stratum is fixed. The *server* stratum varies from 16
at startup to +1 of it's current syspeer, be it an Internet server or
the LOCAL() driver. Your other LAN clients in turn are current stratum
of server +1.


> My server was off-line for so long each day that it's stratum would
> drop to 16 for most of the time, making it useless as a reference for
> my LAN (they'll ignore it).

Server's stratum is not supposed to raise to 16, because LOCAL() driver
artificially extends sync forever. Monthes, years, eons. Show us
experimented ntp.conf, please, there was surely a problem.


> the computers keep time well enough, just free wheeling along
> individually, that they could carry on as they were until the next
> time the LAN was connected to the internet.

So you removed LOCAL()? Without sync machines will diverge. Perhaps
enough to take longer to sync during short online sessions. Or worse
begin to sync with a large frequency peek just when you hangup, then
continue free wheeling but on a this anormal frequency. Finally a client
(re)booted will have false time until next dialup, if ntpd has not died
before on "no servers reachable". Not good.

My advice for you would be to set a 127.127.1.0 stratum 8 prefer on your
server, and another one stratum 14 (but not prefer) on a given client.
This way you have eternal sync, only one sync source at a time, and you
can shutdown server *or* given client for maintenance.

The danger here is sync source hopping and peeks in frequency it can
give. Ntpd is not perfect for your dialup case. People say Chrony is
better suited?


Serge.
--
Serge point Bets arobase laposte point net
.

Relevant Pages

  • Re: Wireless Sync Issue
    ... I did talk to Sprint, and they were clueless, saying there was no ... sometimes making changes in a host file on the server. ... Using an O2 ATOM and unable to sync via GPRS after a USB sync unless I stop ... and the server is accessible from the Internet via ...
    (microsoft.public.pocketpc.activesync)
  • Cannot synchronize to server with local clock
    ... fudged at a high stratum like 8 or 10. ... The *server* stratum varies from 16 ... Without sync machines will diverge. ... and another one stratum 14 on a given client. ...
    (comp.protocols.time.ntp)
  • Re: Wireless Sync Issue
    ... Lots of Windows Mobile 2003 devices work without any problems with the same ... sometimes making changes in a host file on the server. ... Using an O2 ATOM and unable to sync via GPRS after a USB sync unless I stop ... and the server is accessible from the Internet via ...
    (microsoft.public.pocketpc.activesync)
  • Exchange 2003 - ActiveSync - HTTP_403 Error
    ... I set up another exchange server to see what the default ... the demo box not is it hangon out on the Internet. ... I checked the log on the demo server and the syn functions ... pointing at to sync with on the PDA. ...
    (microsoft.public.exchange.connectivity)
  • Re: Doesnt work in Cradle. Repeated conversation.
    ... ActiveSync connection between "automatic" and internet? ... Either way it is getting to the server. ... Sinc your device won't sync in the cradle with the fqdn, ... It will only sync in the cradle if the server name is the Netbios name. ...
    (microsoft.public.pocketpc.activesync)
Loading