Curt LeCaptain wrote:
> Hello,
>  
> I've currently got an NTP server setup on a single host, that I'd like
> to use to synchronize all of my other routers/servers.  My config is as
> follows:
>  
> server 127.127.1.0              # local clock (LCL)
> fudge  127.127.1.0 stratum 10   # LCL is unsynchronized
> 
> server ntp1.cs.wisc.edu
> server ntp3.cs.wisc.edu
> server nss.nts.umn.edu
> server ntp1.chiccp.net
>  
> restrict ntp1.cs.wisc.edu mask 255.255.255.255 nomodify notrap noquery
> restrict ntp3.cs.wisc.edu mask 255.255.255.255 nomodify notrap noquery
> restrict nss.nts.umn.edu mask 255.255.255.255 nomodify notrap noquery
> restrict ntp1.chiccp.net mask 255.255.255.255 nomodify notrap noquery
> restrict 192.168.1.0 mask 255.255.255.192
> restrict 192.168.1.64 mask 255.255.255.192
> restrict 127.0.0.1
> 
> driftfile /var/lib/ntp/drift/ntp.drift 
> logfile   /var/log/ntp   
>  
> The 192.168.1.x addresses are munged for security purposes.  My problem
> is this: at startup, other servers are able to poll my NTP server.
> After about 5-10 minutes, they're no longer able to poll and fail their
> attempts from there on out, as if the service just stops answering.  Any
> suggestions would be great, I'm really lost at this point.
>  
> Curt L.

Is the ntpd process still running when the server stops answering?  Has 
anything been written to /var/log/ntp?

_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions

Reply via email to