Avatar of infedonetwork
infedonetwork
 asked on

Windows Server 2008 keep changing time

Hi.
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?
SBSWindows Server 2008Microsoft Server OS

Avatar of undefined
Last Comment
infedonetwork

8/22/2022 - Mon
cbmm

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

ASKER
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?
cbmm

Its possible they are setup to use an ntp
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
infedonetwork

ASKER
How can I setup the SBS to use NTP?
infedonetwork

ASKER
Looks like the SBS is using the time.windows.com

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:  65.55.21.20)
Last Successful Sync Time: 12/20/12 11:01:41 AM
Source: time.windows.com,0x1
Poll Interval: 6 (64s)
cbmm

Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
infedonetwork

ASKER
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:  86.77.84.80)
Last Successful Sync Time: 12/20/2012 10:55:01 AM
Source: VM IC Time Synchronization Provider
Poll Interval: 10 (1024s)
cbmm

Do you see any errors in the event viewer that are related to time not being able to sync?
infedonetwork

ASKER
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.
Your help has saved me hundreds of hours of internet surfing.
fblack61
cbmm

Run "net time" from a command prompt and show the results.

On your SBS you need to change the 0x1 to 0x9
ASKER CERTIFIED SOLUTION
infedonetwork

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
cbmm

also the 0x1 flag uses less network resource, but not as accurate
infedonetwork

ASKER
Fix problem by searching on Microsoft support site
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.