• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 665
  • Last Modified:

Time problem on w2k3 r2

Hi experts,

I am currently having problem with windows time in one of the newly joined domain member servers.
I have configured DC1 (holding PDC emulator role) to be our ntp server and sync time with external time source. Also, any other server, including other DCs, configured to set nt5ds.
I have confirmed that our DC1 (holding PDC emulator role) is successfully sync time with external time source.


W32tm /stripchart /computer:time source /sample:4 /dataonly
No error

w32tm /monitor
DC1.<domainname>.com ***PDC*** (DC1 IP Address):
ICMP: 0ms delay.
NTP: =0.000000s offset from dc1.(domainname).com
RefID: (unkown) [ip address of external time source]
DC2.<domainname>.com [ip address of dc2]
ICMP: 0ms delay.
NTP: -0.0167689s offset from DC1.<domainname>.com

Also, if I use w32tm /monitor on other member server i get same result as above. Including the server that is having time problem.
I have tried these command on the server that is having problem, w32tm /resync /rediscover, also net stop w32time >> w32tm /unregister >> w32tm /register >> net start w32time still same result... always 1 hours off from the DC1.

When I use net time from the server that is having problem i get result like this.

"Current time at \\DC1 is 3/28/2012 2:40 PM

Local time (GMT-07:00) at \\DC1 is 3/28/2012 3:40 PM    <<< correct time

The command completed successfully."

However, when i use net time on DC1 or any other servers (servers don't have problem)
i get

 
"Current time at \\DC1 is 3/28/2012 3:40 PM     <<< correct time

The command completed successfully."

Also, all of our server time zone is in GMT-08:00 Pacific Time

If anyone could help me solve this issue I’ll be greatly appreciate it.
Thanks!
0
ndoorsinteractive
Asked:
ndoorsinteractive
  • 2
  • 2
1 Solution
 
als315Commented:
Can you run w32tm /tz on problem and other servers?
0
 
ndoorsinteractiveAuthor Commented:
Hi,


Thanks for the comment!
I have run w32tm /tz and confirmed that there is little mismatch. Please see the result below.
Once again thanks a lot!

Result from correct time

Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: 480min (UTC=LocalTime+Bias)
  [Standard Name:"Pacific Standard Time" Bias:0min Date:(M:11 D:1 DoW:0)]
  [Daylight Name:"Pacific Daylight Time" Bias:-60min Date:(M:3 D:2 DoW:0)]


Result from incorrect time

Time zone: Current:TIME_ZONE_ID_STANDARD Bias: 480min (UTC=LocalTime+Bias)
  [Standard Name:"Pacific Standard Time" Bias:0min Date:(M:10 D:5 DoW:0)]
  [Daylight Name:"Pacific Daylight Time" Bias:-60min Date:(M:4 D:1 DoW:0)]


Best,

Jae
0
 
als315Commented:
May be you have not installed some updates (seems there were some changes in time zone or on any reason they were changed manually).
You can compare settings in registry under:
HKEYLOCALMACHINE\Software\Microsoft\Windows\CurrentVersion\TimeZones
or use these methods:
http://support.microsoft.com/kb/914387/en-us
0
 
ndoorsinteractiveAuthor Commented:
Hi,

First of all I would like to thank you for the great help.
I found out that the server missed one of the update and set to old daylight saving beginning date.
After the set the correct daylight saving time server finally works!
Thanks a lot
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now