LocalNTP Registry Setting

I found that there is apparently a way to turn a Windows 2000 server into an
NTP server by enabling a registry key:

\\HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

Value Name: LocalNTP
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = disabled, 1 = enabled)

My question is will this NTP server respond properly to UNIX and other
non-Windows clients? Do I need to configure anything specifically if I
know my clients will be non Windows machines?

--
Will

But I read that the NTP protocol Microsoft is using is a non standard
variant named NT5DS that is not the standard NTP variant. Supposedly the
client signs the request and looks for the server to hand back a similarly
signed response. At least when I run non Windows devices against the NTP
server on a domain controller, that never works.

If you set up a member server - or a stand alone server - as an NTP server,
will they respond to UNIX clients that use standard NTP by using the
specially signed NT5DS responses? If yes, then I guess that would not work
as a generic NTP server.

So it's not a question about which port is used. It's an issue about
whether Microsoft's NTP protocol on a member server is compatible with non
Windows clients.

--
Will


"Kevin D. Goodknecht Sr. [MVP]" <admin RemoveThis @nospam.WFTX.US> wrote in message
news:O2RluHFsGHA.5072@TK2MSFTNGP05.phx.gbl...
> Will wrote:
> > I found that there is apparently a way to turn a Windows 2000 server
> > into an NTP server by enabling a registry key:
> >
> > \\HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
> >
> > Value Name: LocalNTP
> > Data Type: REG_DWORD (DWORD Value)
> > Value Data: (0 = disabled, 1 = enabled)
> >
> > My question is will this NTP server respond properly to UNIX and other
> > non-Windows clients? Do I need to configure anything specifically
> > if I know my clients will be non Windows machines?
>
> NTP uses a standard port, 123 UDP, yes any client querying NTP uses this
> port.