Hello,
I have ntp 4.2 running on Debian testing. I have setup ntp.conf as
follows

driftfile /var/lib/ntp/ntp.drift
statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

server time.nuri.net
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org

restrict default kod notrap nomodify nopeer noquery
restrict 127.0.0.1 nomodify
restrict 10.0.0.0 mask 255.255.0.0 nomodify notrap

my subnet is 10.0.0.0/16. netstat reports ntp server running on port
udp/123. however, when i try ntpdate on some other machine to sync time
with this one, ntpdate says "no server suitable for synchronization
found". could anybody point out what is the mistake i am making ?

poduval@gmail.com wrote:

>Hello,
>I have ntp 4.2 running on Debian testing. I have setup ntp.conf as
>follows
>
>driftfile /var/lib/ntp/ntp.drift
>statsdir /var/log/ntpstats/
>
>statistics loopstats peerstats clockstats
>filegen loopstats file loopstats type day enable
>filegen peerstats file peerstats type day enable
>filegen clockstats file clockstats type day enable
>
>server time.nuri.net
>server 0.pool.ntp.org
>server 1.pool.ntp.org
>server 2.pool.ntp.org
>
>restrict default kod notrap nomodify nopeer noquery
>restrict 127.0.0.1 nomodify
>restrict 10.0.0.0 mask 255.255.0.0 nomodify notrap
>
>my subnet is 10.0.0.0/16. netstat reports ntp server running on port
>udp/123. however, when i try ntpdate on some other machine to sync time
>with this one, ntpdate says "no server suitable for synchronization
>found". could anybody point out what is the mistake i am making ?
>
>  
>
The output of ntpq -p  would be helpful.  It would show us if your 
system has succeeded in synchronizing its clock.  If it has not, no 
other system will consider it to be a "suitable server".

Hello Richard,
After the ntp server ran for a while this is the output from ntp -p

remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
+ntp1.epidc.co.k 192.168.17.8     2 u   23   64  377  311.692  -1745.7
1405.15
+schorle.tedaldi 62.2.116.127     3 u   31   64  377  314.915  -1643.4
1103.84
*dsl027-160-099. 65.212.71.102    2 u   32   64  377  282.133  -1668.3
1093.84
+dsl-217-155-197 132.146.236.132  3 u   25   64  377  317.704  -1648.1
1327.80

The * and + were missing earlier, but after they appeared, the other
systems are synchronizing without a problem. Thank you for the help.

On 2005-01-07, poduval@gmail.com <poduval@gmail.com> wrote:

> server time.nuri.net
> server 0.pool.ntp.org
> server 1.pool.ntp.org
> server 2.pool.ntp.org

Your ntpd will take ~5-10 minutes to achieve sync with these server
lines. If you add 'iburst' to the end of your server lines you'll
achieve sync in ~15-20 seconds.

Your ntpd will not be able to serve time to others until it is synced.

-- 
Steve Kostecke <kostecke@ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/