bbcac
asked on
Domain Time is 4 hours behind Actual Time
We have a newly created parent/child domain infrastructure. All DCs are running Server 2008 Enterprise. We are running the servers on blades and vSphere so the actual servers are virtual. If I understand it right, all servers in the domain, sync from the domain controllers which are fed the time by the root PDC.
The root domain is run by a single dc right now and the time on the at server is exactly 4 hours off. We have the right time set on the HP Blade Chassis (no time zone settings to be found), the blades (no time zone setting to be found). When the systems comes up, it is exactly 4 hours ahead. If I change the time zone to "coordintaed universal time" it shows the right time.
Why is it that if it is set to EST time, the time is 4 hours off in windows. This is causing domain authentication issues. I should also note that the server is set to sync time with time.miscosoft.com and we also tried time.nist.gov
Any help would be appreciated.
The root domain is run by a single dc right now and the time on the at server is exactly 4 hours off. We have the right time set on the HP Blade Chassis (no time zone settings to be found), the blades (no time zone setting to be found). When the systems comes up, it is exactly 4 hours ahead. If I change the time zone to "coordintaed universal time" it shows the right time.
Why is it that if it is set to EST time, the time is 4 hours off in windows. This is causing domain authentication issues. I should also note that the server is set to sync time with time.miscosoft.com and we also tried time.nist.gov
Any help would be appreciated.
ASKER
I didn't see the time zone setting in the blade setup at boot (bl460), or in the chassis settings (HP c3000)
If there is no time zone setting in the BIOS, go with the LOCAL TIME instead.
Clearly, it is off by 4 hours because you are currently in EDT. It will be off 5 hours when the switch to EST occurs in November.
Clearly, it is off by 4 hours because you are currently in EDT. It will be off 5 hours when the switch to EST occurs in November.
ASKER
What do you mean "go with the local time instead"?
My apologies. I was thinking one thing and typing another. I really hate it when that happens... Configure the hardware clock for UTC time, and you should be OK.
I believe the problem with your tyime sync is that the time can only be corrected by a specific quantum -- and I think a 4-hour correction is too large. See http://support.microsoft.com/kb/884776 for info about the Max___PhaseCorrection settings.
This doc may help as well:
http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf
I believe the problem with your tyime sync is that the time can only be corrected by a specific quantum -- and I think a 4-hour correction is too large. See http://support.microsoft.com/kb/884776 for info about the Max___PhaseCorrection settings.
This doc may help as well:
http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf
ASKER
I'm sorry if this is a stupid question, but what hardware clock are you speaking about? The VM, Blade, or Chassis?
And do you know that this is possible?
And do you know that this is possible?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
EST5EDT Etc/GMT-4
ASKER
Thanks
Hopefully this helps you, otherwise someone else might have another idea