Link to home
Start Free TrialLog in
Avatar of infedonetwork

asked on

Windows Server 2008 keep changing time

I have the following scenario.
One physical server running windows 2008 with Hyper V
Two Virtual servers. One is running Windows 2008 SBS and one running windows 2008 with terminal server.
For some reason the SBS start getting the wrong time by 30 minutes.
Because of that the PC's get the wrong time from the server that is different than the terminal server and they can't logon or access it anymore until I correct the time.
Problem is that after one week the problem start again.
Why only the SBS will have this problem?
Avatar of cbmm
Flag of United States of America image

Windows 2008 will get its time from the Bios, not from the internet unless you changed it. You can change it here:
Avatar of infedonetwork


I know but for some reason the other two windows that run on the same box has the correct time.
One thing I see different on this one is date format but that should not make any difference.
It goes 10 min ahead than the other 2.
If it will be the bios would not the other 2 get the same time?
Its possible they are setup to use an ntp
How can I setup the SBS to use NTP?
Looks like the SBS is using the

C:\Users\Administrator>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0782102s
Root Dispersion: 0.3848169s
ReferenceId: 0x41371514 (source IP:
Last Successful Sync Time: 12/20/12 11:01:41 AM
Poll Interval: 6 (64s)
This is from the terminal server

Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 0.0100000s
ReferenceId: 0x564D5450 (source IP:
Last Successful Sync Time: 12/20/2012 10:55:01 AM
Source: VM IC Time Synchronization Provider
Poll Interval: 10 (1024s)
Do you see any errors in the event viewer that are related to time not being able to sync?
No. Only tons of DCOM errors like this one that I think is related to wrong time between the client and the server" DCOM was unable to communicate with the computer shipping using any of the configured protocols.
Run "net time" from a command prompt and show the results.

On your SBS you need to change the 0x1 to 0x9
Avatar of infedonetwork

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
also the 0x1 flag uses less network resource, but not as accurate
Fix problem by searching on Microsoft support site