System Time is 1 hour offset after syncing via Windows Time Servic
- From: Kev <Kev@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 Oct 2008 07:20:02 -0700
One of the Windows 2003 Member Servers within our Domain is keeping its local
System Time incorrectly. We have repeatedly set the System Time to sync via
net time to one of the Time Servers (Domain Controllers). When we perform
this function manually from command line using Net Time, the time syncs to
the time server and gives us back a "successful" message. Unfortunantly, we
see that the local System Clock stays 1 hour behind even after this Windows
Time success sync message.
What could be causing the Windows Server 2003 to keep its local System Time
1 hour off, and not update its time based on time received from the Domain
Controller?
.
- Follow-Ups:
- Re: System Time is 1 hour offset after syncing via Windows Time Servic
- From: Bob the tech guy
- Re: System Time is 1 hour offset after syncing via Windows Time Servic
- From: ThePro
- Re: System Time is 1 hour offset after syncing via Windows Time Servic
- From: Lanwench [MVP - Exchange]
- Re: System Time is 1 hour offset after syncing via Windows Time Servic
- Prev by Date: Re: Error migrating printers using PrintBRM
- Next by Date: Re: System Time is 1 hour offset after syncing via Windows Time Servic
- Previous by thread: how to run a Dedicated Gaming Server on win2k3server ent.X64 editi
- Next by thread: Re: System Time is 1 hour offset after syncing via Windows Time Servic
- Index(es):
Relevant Pages
|