NTP & Windows Time Service client Synchronizing problem

I have read through pages of documentation and message boards today
with no luck. Very quick, here is my problem.

Two Domain Controllers, both running Windows Sever 2003. Goal: Have
the PDC as the authoritative Time Server for the domain (ie member
servers and xp/2000 workstations). Everything I've read has said this
is easy and happens by default in my domain. Wrong!

I am confident the Domain Controllers are working correctly. We'll
call them DC1 (also the PDC) and DC2. For example, DC2 is checking
with DC1 and confirming it's a valid time source, and synchronizing.


However, my XP box logs into the domain, synchs with DC1 (or so I read
via the Event Viewer), but nothing happens. My XP clock is still set
for Pacific Time (I'm Central).

I've restarted services numerous times. I've tried using Group Policy
the following way: By placing XPMachine in a Test OU. I enable NTP
Client and configure to use Domain Heirarchy; while also applying a GPO
on my domain controllers as NTP Servers. My XP clock still doesn't
update.

In fact, during all troubleshooting, the XP workstation still displays
the current output: "C:/net time /querysntp" - time.windows.com

by the way, DC2 outputs DC1 on the same query. DC1 does not have a
valid time source (since it sits atop the hierachy and I have no
external server programmed)

also, I know I can manually configure a new time server using the w32tm
command. But how would I apply to pcs in the domain that I don't know
about? I don't want to manually set the time server, I'd like to have
it changed automatically, if possible.

I just want the XP box to synch, then I can apply the settings to my
domain to ensure no misconfigured clocks disrupt users. Any ideas??

I hate daylight savings...

For synching your server to an external time source, see
KB Article ID 875424



Some misc troubleshooting info:

a.. To see what external NTP server your server is configured for, run
"net time /querysntp" from a command prompt.


a.. As for the client PCs (at least 2K/XP), if their w32time service is
running and they are joined to a domain, they will automatically look to the
forest root for a time server. Every time a client (2K/XP) or the server
tries or really does synchronize time it generates an entry for that in the
event System log. The information there is really helpful to find out where
to look at. To test your settings check manual by use of NET TIME /SET at
the command prompt. You will see the server used and the actual time
differences.


a.. There is a hotfix for W2k3 server if time is not sync'ing:
http://support.microsoft.com/?kbid=832261


a.. Verify that the "Windows Time" service (w32time) is running and set to
automatic startup on the server and clients (saw one Disabled!).


a.. On the W2k3 server, check the time zone setting is correct.


a.. Check:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Parameters
In the right panel, double-click 'Type'. If the value data is 'NoSync',
change it to 'Nt5DS'. (hj-if use above procedure, sets it to NTP vs Nt5DS).
Go to services console, restart the Windows Time service.
Hope this helps, dtocco1

Harvey Juster

Thanks for the response Harvey,

I have posted comments right below your comments:

"" a.. To see what external NTP server your server is configured for,
run
"net time /querysntp" from a command prompt. ""

If ran on DC1 - also the domain PDC - the output is NONE - since it's
atop the hierarchy. If ran on DC2, the output is DC1.

If ran on random XP boxes throughout my domain - and current
problematic pc - the output is time.windows.com

""a.. As for the client PCs (at least 2K/XP), if their w32time service
is
running and they are joined to a domain, they will automatically look
to the
forest root for a time server. Every time a client (2K/XP) or the
server
tries or really does synchronize time it generates an entry for that in
the
event System log. The information there is really helpful to find out
where
to look at. To test your settings check manual by use of NET TIME /SET
at
the command prompt. You will see the server used and the actual time
differences. ""

If ran on the troublesome XP pc, the out put is:

Current time on //PDC - 0600 (Wrong Time, PST - 2 hours off)
Local time on //PDC - 0800 (Correct Time, CST)

If ran on PDC, the output is:

Current time on //PDC - 0800 (Correct Time, CST)
Local time on //PDC - 0800 (Correct Time, CST)

Everytime the XP machine logs into the domain, an event is created in
the Event Viewer saying that XP client has synchronized with PDC. This
is the W32Time service.

"" a.. There is a hotfix for W2k3 server if time is not sync'ing:
http://support.microsoft.com/?kbid=832261""

Isn't this fix included in W2k3 server SP1 ?

""a.. Check:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Parameters
In the right panel, double-click 'Type'. If the value data is
'NoSync',
change it to 'Nt5DS'."

This is set on my PDC

dtocco1,

I have posted comments right below your comments:
>
> "" a.. To see what external NTP server your server is configured for,
> run
> "net time /querysntp" from a command prompt. ""
>
> If ran on DC1 - also the domain PDC - the output is NONE - since it's
> atop the hierarchy. If ran on DC2, the output is DC1.

My DC looks like this:
C:\Documents and Settings\Administrator>net time /querysntp
The current SNTP value is: time.nist.gov,0x8

>
> If ran on random XP boxes throughout my domain - and current
> problematic pc - the output is time.windows.com

OK, my clients say time.windows.com,0x1 - not sure if this is an issue.
>
> ""a.. As for the client PCs (at least 2K/XP), if their w32time service
> is
> running and they are joined to a domain, they will automatically look
> to the
> forest root for a time server. Every time a client (2K/XP) or the
> server
> tries or really does synchronize time it generates an entry for that in
> the
> event System log. The information there is really helpful to find out
> where
> to look at. To test your settings check manual by use of NET TIME /SET
> at
> the command prompt. You will see the server used and the actual time
> differences. ""
>
> If ran on the troublesome XP pc, the out put is:
>
> Current time on //PDC - 0600 (Wrong Time, PST - 2 hours off)
> Local time on //PDC - 0800 (Correct Time, CST)
>

My XP PCs show:
C:\Documents and Settings\administrator.TBE1>net time /set
Current time at \\SHAMUS is 4/6/2006 6:13 PM
The current local clock is 4/6/2006 6:13 PM
Do you want to set the local computer's time to match the
time at \\SHAMUS? (Y/N) [Y]:

Both of your lines above reference the PDC. On mine, one is the DC (Shamus)
and one the "local computer".

I have to wonder if you PDC is indeed set up as a time server ont he domain.
Maybe try the steps in the KB article I sent you? Could this be a firewall
issue - maybe disable all of them for a short test.

Regards,
Harvey

> If ran on PDC, the output is:
>
> Current time on //PDC - 0800 (Correct Time, CST)
> Local time on //PDC - 0800 (Correct Time, CST)

>
> Everytime the XP machine logs into the domain, an event is created in
> the Event Viewer saying that XP client has synchronized with PDC. This
> is the W32Time service.
>
> "" a.. There is a hotfix for W2k3 server if time is not sync'ing:
> http://support.microsoft.com/?kbid=832261""
>
> Isn't this fix included in W2k3 server SP1 ?
>
> ""a.. Check:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Parameters
> In the right panel, double-click 'Type'. If the value data is
> 'NoSync',
> change it to 'Nt5DS'."
>
> This is set on my PDC
>