Time Service errors

[MartinHTN]

Hello:

We have only 1 NT domain and put the first Windows Server
2003 AD DC in this past weekend. Everything seems to be
working fine except the time service. During the upgrade,
we used a temporary NT 4.0 PDC (TEMPPDC) and upgraded it
to 2003. About an hour after that we dcpromo'd a 2003
server (NEWPDC) and then transferred all the FSMO roles
from TEMPPDC to NEWPDC and then dcpromo'd TEMPPDC to
remove AD from it. No major errors of concern were
received during either stage. Now I get the errors below.
Clicking on the help and support links doesn't give much
info.

Also, I noticed that once a 2003 server is a made a domain
member, the Internet time option in the Date and Time
properties is no longer available. That being the case,
how do I direct my current PDC Emulator (NEWPDC) to use
one of the Internet time servers? I'm also confused as to
the differences between using the "net time" and "w32tm"
commands. A "net time /querysntp" from NEWPDC shows the
following:

C:\>net time /querysntp
The current SNTP value is: time-a.nist.gov
The command completed successfully.

You would think this is a simple, straight-forward
setting, but I can't seem to figure it out. Thank you.

Below are the time related errors in the System Logs no
TEMPPDC and NEWPDC:

From TEMPPDC:

Event ID 26:
Time Provider NtpClient: The response received from domain
controller newpdc.fabrikam.com has a bad signature. The
response may have been tampered with and will be ignored.

For more information, see Help and Support Center at
[url]http://go.microsoft.com/fwlink/events.asp[/url].

*********************************

From NEWPDC I get the following 3 errors 15 minutes apart
from each other every hour:

Event ID 38: (I get this first)
The time provider NtpClient cannot reach or is currently
receiving invalid time data from de1smsdctemp.pca.phillips-
cohen.com (ntp.d|10.2.2.13:123->10.2.2.11:123).

For more information, see Help and Support Center at
[url]http://go.microsoft.com/fwlink/events.asp[/url].

--------------------------------
Event ID 14: (I get this second)
The time provider NtpClient was unable to find a domain
controller to use as a time source. NtpClient will try
again in 30 minutes.

For more information, see Help and Support Center at
[url]http://go.microsoft.com/fwlink/events.asp[/url].

--------------------------------
Event ID 24: (I get this third)
Time Provider NtpClient: No valid response has been
received from domain controller de1smsdctemp.pca.phillips-
cohen.com after 8 attempts to contact it. This domain
controller will be discarded as a time source and
NtpClient will attempt to discover a new domain
controller from which to synchronize.

For more information, see Help and Support Center at
[url]http://go.microsoft.com/fwlink/events.asp[/url].

[MartinHTN]

I wanted to add that some of workstations and member
servers do see that NEWPDC is the time server and are
getting their time from it. If I do a "net time" from a
client it will show the current time at NEWPDC.

[MartinHTN]

I used the following 2 commands:

w32tm /config /syncfromflags:manual /manualpeerlist:time-
a.nist.gov

w32tm /config /update

After that I got the following event on NEWPDC:

Event ID 37:
The time provider NtpClient is currently receiving valid
time data from time-a.nist.gov (ntp.m|0x0|10.2.2.13:123-

>129.6.15.28:123).

So I think this is working now.