Hi,
In general the device which adjusts the time (NTP Request) authenticates the
source of the time information (which sends NTP Update). The server only
derives the Key Number but does not verify the hash. Try to configure it
similarly to like client, maybe then it will force it to verify the hash as
well (but not sure if it is going to change anything in client-server
relationship).
For NTP peers, because they adjust time based on each other, it makes
perfect sense to authenticate each other as well.
You can always use the NTP Access Control on the client/server to specify
who can you accept NTP Requests/NTP Updates from.
Cheers,
Piotr
On Tue, Jun 8, 2010 at 3:06 PM, Abiola Jewoola <biola_y2k_at_yahoo.com> wrote:
> Hello GS
>
> Is it possible for NTP server and client to authenticate each other. I know
> that if the two devices are peers they can authenticate each other.
>
> Regards
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Piotr Kaluzny CCIE #25665 (Security), CCSP, CCNP Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com Blogs and organic groups at http://www.ccie.netReceived on Tue Jun 08 2010 - 16:28:28 ART
This archive was generated by hypermail 2.2.0 : Sun Aug 01 2010 - 09:11:37 ART