XP Pro Time Synch Issues

[Roger Johnson]

Hello all,



I am having an issue where all the windows xp pro machines on my win2k AD
network are having problems completing a time synch with the domain
controllers. They are getting a status of completed successfully when the
script runs, but the time never synchs up, but none off the win2k pro boxes
are having any issues. I am getting the following errors in the event log on
all the XP boxes:



Source W32Time Event:29

The time provider NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently accessible. No
attempt to contact a source will be made for 15 minutes. NtpClient has no
source of accurate time.

Source W32Time Event:24

Time Provider NtpClient: No valid response has been received from domain
controller "servername" 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.

Source W32Time Event:29

The time provider NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently accessible. No
attempt to contact a source will be made for 15 minutes. NtpClient has no
source of accurate time.



Does anyone have any idea what could be causing the problem and how I can
correct it.

Regards,



Roger

 

[Mike Brannigan [MSFT]]

Hello all,



I am having an issue where all the windows xp pro machines on my win2k AD
network are having problems completing a time synch with the domain
controllers. They are getting a status of completed successfully when the
script runs, but the time never synchs up, but none off the win2k pro boxes
are having any issues. I am getting the following errors in the event log on
all the XP boxes:

Roger,

What script ???
You do not need a script to time synch in a Windows 2000/2003 Domain with
Windows 2000/XP clients.
All servers and clients perform time synch in accordance with the hierarchy
documented in TechNet. This is required by default for Kerberos to operate
successfully.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Roger Johnson]

At logon I have a logon script that runs that runs the net time command to
synch the client time with the time server which is my domain controller.
This completes successfully, but the time never synchs. Is there a time out
period on the windows time service that can be adjusted.

Roger

 

[Mike Matheny]

That script is not needed - all W2K and XP PCs on a domain sync to the DC.
Remove that script and on the problem PC's, at a command prompt, enter w32tm
/register and see if that gets things moving - there should be an entry in
the event log under w32time stating that the pc is now syncing the time with
your DC.

 

[Roger Johnson]

The script however isn't really intended for the win2k and xp systems, but
rather for the nt4 and 9x systems. I am planning on building some logic into
the script that will avoid running the time synch part of the script aginst
the systems win2k and above. However this still leaves me with the time
synch issues with xp systems.

Earlier I ran the w32tm /resync which seemed to correct the error messages
on the xp box that I tested it on. In the event that it is actually network
latency that is causing the problem is there a way to configure a longer
timeout for the time synch. Also, does anyone know if the system isn't
rebooted for a couple of days does the time service try to resynch itself
and if so how offen does it do it.

Thanks again for all you help!

Roger

 

[Mike Matheny]

Ok then, you need to use Kixtart to write a logon script that only runs on
the nt4 and 9x systems.