Windows 2000 as NTP Server

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

In our environment, we have both Windows and non-Windows servers. I'd like to
set up a common configuration for time synchronization. Currently I'm doing
testing with Windows 2000 Professional ( donj't want to disrupt a production
server, especially a DC ). Anyway, I've gone through the registry changes on
my desktop ( changed the w32time\parameters\LocalNTP -> 1 ) and updated the
time from an NTP server on the internet. I next used w32time to point a 2nd
Windows 2000 pro machine to the 1st - it updated its time as expected.

I then talked to one of our Unix guys and he configured a test Unix server
to use my desktop as its NTPserver. Well, that didn't work. The Unix system
times out while trying to connect to the NTP server. Network connectivity
does exist and was verified by pinging my desktop and there is no Ip
filtering going on.

Through further research I found that Windows 2000 actually uses SNTP, not
NTP. Could this be the casue of my problem? NTP and SNTP data packets are
supposed to be identical, but I don't know how client to server connectivity
would be handled.

Any help would be appreciated.

BTW, it appears that Windows 2003 actually uses NTP, so maybe it would work
with a Unix client.