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\P arameters

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

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\P arameters
>
> 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.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

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]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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\P arameters
> >
> > 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.