Hi, ALl

Forgive me if I asked here with wrong question.

I have server named lab-time to provide ntp service for all PCs of our
lab.lab-time has RHEL AS3 installed. Also I have win2003 PC named lab01 with the following ntp sync order.

lab01(win2003) => lab-dc(domain controller) ==> lab-time(RHEL3)

However, recently I get the following error event from lab01 which is win2003.

http://support.microsoft.com/kb/875424/EN-US/

I tried to troubleshoot lab01 as the link above, However, problem is still
there.

So I wonder whether lab-time(RHEL3) needs to do some configure if it should provide ntp service to windows PCs. Any idea?

Yep...Windows is junk, is the best idea I can give you. Had this same problem, and it boils down to Windows wanting to use (surprise!) a Windows-based time server, and not fully supporting standards, like NTP.

Your time server is fine, and there's nothing you can do to it, to make Windows like it. In my environment, we've got 4 time servers, using GPS data, and atomized PPS kernels. EVERYTHING (mainframes, unix/linux, routers, switches, etc.), synchs to it. The ONLY machines that have problems are the Windows boxes. Following the procedure in the link you posted, works sometimes...sometimes you've got to do it multiple times, with reboots.

Check your /etc/ntp.conf file. Especially the restrict directives. Remove the nopeer and noquery options from the restrict default ... directive.

Hi, fpmurphy

==>
Do u mean to remove the nopeer and noquery options from restrict default directive as follows?

restrict default ***** nopeer noquery ==> restrict default ignore

Can u tell me the reason to remove nopeer and noquery from restrict default directive? Because I see nopeer is to prevent the remove machine
to set the NTP server own time, I think nopeer should be there if I
understand the nopeer option function well.

noquery means "Deny ntpq and ntpdc queries. Time service is not affected."
I am not sure why we need remove noquery if the ntp client is windows pc.