ntpdate[5498]: no server suitable for synchronization found

On Sat, Jun 16, 2007 at 03:29:33PM +0530, anup wrote:
> I am trying to setup NTP client inside my network using public time server.
> I used " ntpdate -ud 3.asia.pool.ntp.org " it gives the following error
> messaage..
>
> 202.234.64.222: Server dropped: no data

Can you try a specific server?

Also, I found that ntpdate was less helpful to me than full ntp (which
now comes with a 'quick' option). The ntp docs say that they are hoping
now that ntpdate dies a gracefull death as people switch to ntp.

Doug.

--

On 6/16/07, anup wrote:
> I am trying to setup NTP client inside my network using public time server.
> I used " ntpdate -ud 3.asia.pool.ntp.org " it gives the following error
> messaage..
[...]
> 16 Jun 15:20:26 ntpdate[5498]: no server suitable for synchronization found
>
> Please help in this regard

I've had good luck with the command
# ntpdate-debian
which is also in the ntpdate package. You don't need to give it any
arguments -- it will automatically look for one of the debian NTP
servers: [0-3].debian.pool.ntp.org

--
Michael A. Marsh
http://www.umiacs.umd.edu/~mmarsh
http://mamarsh.blogspot.com
http://36pints.blogspot.com

--

I assume you are in Asia. If so, run the following script and
examine the output. Pick three hosts that look best and use them in
place of "3.asia.pool.ntp.org".

Script:

--------cut here---------------
for i in 0 1 2 3
do
host $i.asia.pool.ntp.org
done | while read x
echo ""
do y="$(echo $x | sed 's/^.*has address //')"
ping -c10 -q $y
host $y
done
--------cut here---------------

Criteria for a "good" host:

no more than 10% packet loss.
max round trip time is acceptably low
deviation (mdev or stddev, depending on which version of ping) of
round trip time is acceptably low.

Enjoy!

Rick

--

Yes I am in Asia.
I picked up three server from the script as fallows.
202.234.64.222
124.10.47.8
152.118.24.8
And run the ntpdate command,  But still i am facing the same problem
and got the following Error.

[root@localhost etc]# ntpdate -ud 152.118.24.8
18 Jun 10:08:55 ntpdate[8675]: ntpdate 4.2.0a@1.1190-r Mon Oct 11
09:10:21 EDT 2004 (1)
Looking for host 152.118.24.8 and service ntp
host found : uicsgtw.cs.ui.ac.id
transmit(152.118.24.8)
transmit(152.118.24.8)
transmit(152.118.24.8)
transmit(152.118.24.8)
transmit(152.118.24.8)
152.118.24.8: Server dropped: no data
server 152.118.24.8, port 123
stratum 0, precision 0, leap 00, trust 000
refid [152.118.24.8], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036 11:58:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036 11:58:16.000
transmit timestamp:  ca208ae3.c947bedb  Mon, Jun 18 2007 10:08:59.786
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

18 Jun 10:09:00 ntpdate[8675]: no server suitable for synchronization
found

Is it necessary to access time server only on Live server in my
organization or i can access it on internal network PC?

----- Original Message ----- From: "Rick Thomas"
<rbthomas55@pobox.com>

To: "anup" <anup.behare@einfochips.com>

Cc: <debian-user@lists.debian.org>

Sent: Sunday, June 17, 2007 10:54 AM

Subject: Re: ntpdate[5498]: no server suitable for synchronization
found

I assume you are in Asia.  If so, run the following script and  examine
the output.  Pick three hosts that look best and use them in  place of
"3.asia.pool.ntp.org".

Script:
--------cut here---------------
for i in 0 1 2 3

do

host $i.asia.pool.ntp.org

done | while read x

echo ""

do y="$(echo $x | sed 's/^.*has address //')"

ping -c10 -q $y

host $y

done

--------cut here---------------

Criteria for a "good" host:

no more than 10% packet loss.

max round trip time is acceptably low

deviation (mdev or stddev, depending on which version of ping) of 
round trip time is acceptably low.

Enjoy!

 Rick