Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat. The purpose of this eBook is to educate the reader about ransomware attacks.
Solved
Windows Server 2008 keep changing time
Posted on 2012-12-20
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?
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?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
7
6
13 Comments
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?
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?
Looks like the SBS is using the time.windows.com
C:\Users\Administrator>w32
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)
C:\Users\Administrator>w32
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)
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)
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)
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
On your SBS you need to change the 0x1 to 0x9
I fix it by running the following command on both server:
w32tm /config /manualpeerlist:us.pool.nt
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
w32tm /config /manualpeerlist:us.pool.nt
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
Featured Post
Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them.
Troubleshooting Steps:
Connect via h…
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade. That can be fixed so it 'works around' agai…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention.
Multiple USB devices need t…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012.
Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
Suggested Courses
Course of the Month9 days, 5 hours left to enroll
721 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.