Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to configure a Windows XP NTP client to authenticate to a local NTP server on our closed network. How can I make this happen?

One article I've found for configuring the client to talk to a remote server is: I would also appreciate if someone could verify if the 2nd part (configuring the windows time service to use an external time source) is what I'm looking for as far as configuring the WinXP client goes.

As far as authentication goes, something similar that we did on our routers/switches is:

RouterOne(config)#ntp authenticate
RouterOne(config)#ntp authentication-key 11 md5 MyKey
RouterOne(config)#ntp trusted-key 11
RouterOne(config)#ntp server key 11

Is a domain environment required?

share|improve this question
up vote 2 down vote accepted

Windows clients can't do this as they use SNTP rather than full NTP. They can, however, use Kerberos for authentication when part of a domain and getting time from a local Windows server.

You could try something like the Meinberg NTP client as this is a proper NTP client.

share|improve this answer
So just to be clear: windows clients cannot authenticate to NTP by default in a non-domain environment because they are using SNTP, rather than the full NTP suite. They can only do it unauthenticated? – Hortonew Dec 7 '11 at 12:25
Correct. SNTP is only a limited subset of NTP and the Windows implementation doesn't really provide much in the way of configuration. I use the Meinberg client for machines that need greater accuracy and specific configuration settings. – James O'Gorman Dec 7 '11 at 12:29

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.