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

It's starting to look like you have firewall problems.

Is port 123 (ntp) allowed through your organizational firewall?

If not, you may need to talk to your network administrators.

Rick

On Jun 18, 2007, at 12:53 AM, anup wrote:

> 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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Thanks Rick.
That was the problem of firewall.

~Anup


----- Original Message -----
From: "Rick Thomas" <rbthomas55@pobox.com>
To: "anup" <anup.behare@einfochips.com>
Cc: <debian-user@lists.debian.org>
Sent: Monday, June 18, 2007 2:03 PM
Subject: Re: ntpdate[5498]: no server suitable for synchronization found


> It's starting to look like you have firewall problems.
>
> Is port 123 (ntp) allowed through your organizational firewall?
>
> If not, you may need to talk to your network administrators.
>
> Rick
>
> On Jun 18, 2007, at 12:53 AM, anup wrote:
>
>> 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
>
>
>
> - This message has been scanned for viruses, spam and dangerous content by
> www.CleanMailGateway.com, and is believed to be clean.
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org