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

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?
0
infedonetwork
Asked:
infedonetwork
  • 7
  • 6
1 Solution
 
cbmmCommented:
Windows 2008 will get its time from the Bios, not from the internet unless you changed it. You can change it here:
0
 
infedonetworkAuthor Commented:
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?
0
 
cbmmCommented:
Its possible they are setup to use an ntp
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
infedonetworkAuthor Commented:
How can I setup the SBS to use NTP?
0
 
infedonetworkAuthor Commented:
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)
0
 
cbmmCommented:
0
 
infedonetworkAuthor Commented:
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)
0
 
cbmmCommented:
Do you see any errors in the event viewer that are related to time not being able to sync?
0
 
infedonetworkAuthor Commented:
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.
0
 
cbmmCommented:
Run "net time" from a command prompt and show the results.

On your SBS you need to change the 0x1 to 0x9
0
 
infedonetworkAuthor Commented:
I fix it by running the following command on both server:
w32tm /config /manualpeerlist:us.pool.ntp.org
Restart windows time services.
This way they both have the same NTP server.
Before they had different time server and that could cause the problem even if it should not.
The one that had the problem was grabbing the time from time.windows.com
Now they both grab from the same spot.
I will keep en eye on for a week to see if it work the way it suppose to
0
 
cbmmCommented:
also the 0x1 flag uses less network resource, but not as accurate
0
 
infedonetworkAuthor Commented:
Fix problem by searching on Microsoft support site
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

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