Link to home
Start Free TrialLog in
Avatar of okamon
okamon

asked on

why the time on my DC is always wrong?

I only have 1 DC in my domain, windows 2003. here is my setting:

NTP server: ca.pool.ntp.org,0×8
Enabled = 1

It's always 1 hour delay
Avatar of DCTech85
DCTech85

its delayed all year round or just after day light savings time?
ASKER CERTIFIED SOLUTION
Avatar of Thommy
Thommy
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If you mean that it is always off by one hour, then your timezone setting is inaccurate.  NTP servers like ca.pool.ntp.org transmit time/date data.  The local machine recieves it and uses its timezone setting to hash the information it recieved from the timesource.  There have been many changes to timezone information within the last few years.  Make sure your server has all the timezone patches.

See:  http://support.microsoft.com/gp/cp_dst
Avatar of okamon

ASKER

the patch fixed the problem!!! My time zone was correct, that was not the issue.... is it because I am running DC in VM?? and NTP server: ca.pool.ntp.org,0×8 , can any one tell me what is 0x8 mean?
It was time.windows.com,0x1 before I remember......
Avatar of okamon

ASKER

just an update, even though the DC is fixed... but the member server 9also a VM) still show incorrect time.. time zone is correct. So do I also run the fix? Is this a known bug? even not with VM?
Just an obvious note:  If the time was set under the previous timezone and you changed the timezone and/or patched it, you may have to actually correct the time once.  

Over the last couple of years there have been several time "fixes" that MS had to address, so you should have/install the time patches.

The links posted should address it.  Let us know if it does not.