IT_Fanatic
asked on
W32Time Warnings
I had an issue last week and needed to call Microsoft and Yesterday one of our Hyper-V VM's is getting W32Time errors. The errors are the following.
First I see this.
Event ID 38 W32Time
The time provider NtpClient cannot reach or is currently receiving invalid time data from PDCSERVER.com (ntp.d| IP of VM with errors->IP of PDC).
Than a few minutes later followed by these errors and warnings every 20-30 minutes
Event ID 24 W32Time
Time Provider NtpClient: No valid response has been received from domain controller PDC.com after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize.
Event ID 29 W32Time
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
The crazy thing is that it is in fact syncing to the tee with the PDC. Meaning the seconds minutes etc.. are perfectly synced. This is the only VM that has the issue. Microsoft didn't want to touch it because the VM is WinServer2003 but the tech said just run the followin
w32tm /resync /rediscover
net time (to make sure its getting it from the PDC)
Once I run w32tm /resync /rediscover the errors go away for a while and the message above goes from receiving invalid time to valid time.
How can I fix this because I find it weird that it is perfectly synced and I see these errors and warning.
The PDC is a physical server running Win Server 2008 Standard R2 with the Hyper-V role installed.
The server with the warnings is a VM running inside Hyper-V and the OS is Win Server 2003.
Thanks for your help all of you.
First I see this.
Event ID 38 W32Time
The time provider NtpClient cannot reach or is currently receiving invalid time data from PDCSERVER.com (ntp.d| IP of VM with errors->IP of PDC).
Than a few minutes later followed by these errors and warnings every 20-30 minutes
Event ID 24 W32Time
Time Provider NtpClient: No valid response has been received from domain controller PDC.com after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize.
Event ID 29 W32Time
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
The crazy thing is that it is in fact syncing to the tee with the PDC. Meaning the seconds minutes etc.. are perfectly synced. This is the only VM that has the issue. Microsoft didn't want to touch it because the VM is WinServer2003 but the tech said just run the followin
w32tm /resync /rediscover
net time (to make sure its getting it from the PDC)
Once I run w32tm /resync /rediscover the errors go away for a while and the message above goes from receiving invalid time to valid time.
How can I fix this because I find it weird that it is perfectly synced and I see these errors and warning.
The PDC is a physical server running Win Server 2008 Standard R2 with the Hyper-V role installed.
The server with the warnings is a VM running inside Hyper-V and the OS is Win Server 2003.
Thanks for your help all of you.
Lionel MM
Do you have the the "Time Synchronization" checked in the Hyper-V settings for the VM? (Can be found under Management section of settings, under Integration). If you do un-check that. I too had issues with time when I had that checked--when that is checked the VM tries to synch its time to both the domain time and then also to the physical time of the Hyper-V server.
ASKER
Had to call Microsoft because I had an issue last week on Friday with Replication and they fixed it but Monday started seeing the W32tm warning on 2 VM's out of 3. But all the PC's were synced and even the VM's who had the errors with the time from the PDC. Prior to the issues the PDC would get the time from the local system clock. Now I guess Microsoft did something that its getting the time from time.microsoft..... Not sure it thats a problem but its a new change.
So I called today to revert the changes they made on Monday They Disabled VMCI on the physical server hyper-v role, PDC server and the second DC VM Monday. I said lets go back prior because I never had any issues prior to calling Friday for support.
So the severs are syncing nicely but are off by 15 seconds or less. If that normal?
Also the user PC's are off by a minute or less. I've done this on the PC's
net stop w32time & net start w32time
w32tm /resync /rediscover (ran maybe twice until it gets the VMCI or time from the PDC instead of the second DC VM)
w32tm /query /status (once it says time from VMCI or PDC on the vm i do the next command)
net time
Is it normal for machines to be off by a minute or less even if they are supposedly getting the time from the PDC are the PC says it is?
So I called today to revert the changes they made on Monday They Disabled VMCI on the physical server hyper-v role, PDC server and the second DC VM Monday. I said lets go back prior because I never had any issues prior to calling Friday for support.
So the severs are syncing nicely but are off by 15 seconds or less. If that normal?
Also the user PC's are off by a minute or less. I've done this on the PC's
net stop w32time & net start w32time
w32tm /resync /rediscover (ran maybe twice until it gets the VMCI or time from the PDC instead of the second DC VM)
w32tm /query /status (once it says time from VMCI or PDC on the vm i do the next command)
net time
Is it normal for machines to be off by a minute or less even if they are supposedly getting the time from the PDC are the PC says it is?
no this is not normal they need to be exact. I must refer you back to my earlier commentshttps://www.experts-exchange.com/questions/28708620/W32Time-Warnings.html?anchorAnswerId=40947877#a40947877
did you check the settings I asked you about and if so what are they now?
did you check the settings I asked you about and if so what are they now?
ASKER
I checked and all 3 VM's and they do have "Time Synchronization" checked in the Hyper-V settings for the VM. I unckecked it for one of the VM's to see if the warnings go away. Do I need to reboot that VM or its fine as is?
you will need to run the net stop and net start for the time server again. if that doesn't do it reboot just to be sure and if that doesn't do it then it is something else.
ASKER
Microsoft called me back today since we had a prior ticket open and this is what we did to see if it fixes the issue. Let me know your thoughts.
We have 2 Physical Servers
1 Server running WinServer2008 Standard R2 which is the PDC, DNS DHCP and with the Hyper-V role installed running 3 VM's
The 3 VM's are (The second DC, File Server and a Finance Server)
The Other physical server is running Windows Storage Server 2008 R2 (This is where we back up our images to)
Microsoft unchecked the "Time Synchronization" in the Hyper-V settings for each VM which are (The second DC, File Server and a Finance Server).
Then we logged into each VM and did the following
net stop w32time & net start w32time
We tried w32tm /query /status and it said CMOS clock for the source so we did
w32tm /resync /rediscover
than once again
w32tm /query /status Now the time source says the PDC physical server
We ran this on the 2 Server2008 VM's the 1 VM thats Server 2003 we did
net stop w32time & net start w32time
w32tm /resync /rediscover
net time /querysntp This source says time.microsoft which is the source the PDC is using.
The PDC and DC VM are sync perfectly the other two are off by 5 seconds or less. Guessing with time it should be synced. Microsoft said now see if the errors dont come back.
Do you agree with these steps taken?
We have 2 Physical Servers
1 Server running WinServer2008 Standard R2 which is the PDC, DNS DHCP and with the Hyper-V role installed running 3 VM's
The 3 VM's are (The second DC, File Server and a Finance Server)
The Other physical server is running Windows Storage Server 2008 R2 (This is where we back up our images to)
Microsoft unchecked the "Time Synchronization" in the Hyper-V settings for each VM which are (The second DC, File Server and a Finance Server).
Then we logged into each VM and did the following
net stop w32time & net start w32time
We tried w32tm /query /status and it said CMOS clock for the source so we did
w32tm /resync /rediscover
than once again
w32tm /query /status Now the time source says the PDC physical server
We ran this on the 2 Server2008 VM's the 1 VM thats Server 2003 we did
net stop w32time & net start w32time
w32tm /resync /rediscover
net time /querysntp This source says time.microsoft which is the source the PDC is using.
The PDC and DC VM are sync perfectly the other two are off by 5 seconds or less. Guessing with time it should be synced. Microsoft said now see if the errors dont come back.
Do you agree with these steps taken?
yes but the time should not be off by 5 seconds it should synch up right away and stay synched. On the two that are not synched what does this command give you
net time
Also run this command on the systems that are in synch and what do they say
Which on of this systems is your domain time server?
net time
Also run this command on the systems that are in synch and what do they say
Which on of this systems is your domain time server?
ASKER
PDC (Main Physical Server, This is the timer server) Net Time = The name of this server
VM (File Server) Net Time = THE PDC Server
VM (Finance Server) Net Time = THE PDC Server
VM (Second DC) Net Time = THE PDC Server
Backup Server (Physical Server) Net Time = THE PDC Server
VM (File Server) Net Time = THE PDC Server
VM (Finance Server) Net Time = THE PDC Server
VM (Second DC) Net Time = THE PDC Server
Backup Server (Physical Server) Net Time = THE PDC Server
OK that's very good. Now on the two that are not 100% accurate run this command
Net Time \\The-PDC-Server /set /y
and let me know if it now stay accurate
these are all on the same subnet, right (IP addresses)?
Net Time \\The-PDC-Server /set /y
and let me know if it now stay accurate
these are all on the same subnet, right (IP addresses)?
ASKER
Ok here we go again and so that i can break down my environment without confusion.
We have 2 Physical Servers
1 Physical Server running WinServer2008 Standard R2 which is the PDC, DNS DHCP and with the Hyper-V role installed running 3 VM's
3 VM's (The second DC, File Server and a Finance Server)
The Other physical server is running Windows Storage Server 2008 R2 (This is where we back up our images to)
Ok so i did Net Time \\The-PDC-Server /set /y and everything synced perfectly and after a while All Vm's and the other Physical server were off again by a few seconds. Now this morning I see the logs below on the VM's and the other Physical server but nothing on the PDC Physical server.
VM File Server:
Event ID 50 9/2/2015 1:26:42AM
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
Event ID 24 9/2/2015 5:43:06AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize.
Event ID 29 9/2/2015 5:43:06AM
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
Event ID 37 9/2/2015 5:58:06AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
VM Finance Server
Event ID 24 9/2/2015 6:40:44AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Event ID 37 9/2/2015 6:55:45AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
VM Second DC Server
Event ID 24 9/2/2015 4:50:43AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Event ID 37 9/2/2015 5:05:44AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
Event ID 24 9/2/2015 6:39:35AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Event ID 37 9/2/2015 8:00:24AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
Event ID 24 9/2/2015 9:25:57AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Physical Windows Storage Server 2008 R2
Event ID 24 9/2/2015 5:36:53AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization.
Event ID 37 9/2/2015 7:00:17AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
Event ID 24 9/2/2015 8:25:46AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization.
So for me to fix this and get all the errors away for a while I tried to go to my second DC VM since I was on it at the time and ran
w32tm /resync
I get a response saying could not access contact time source something of the sort. So to fix this I logged into the Physical PDC server and ran
w32tm /resync
Once the output was successful I was able to go back to the second DC VM and ran
w32tm /resync
with sucess and than followed by
w32tm /query /status (Shows the times source of the PDC)
net time (Shows the PDC).
I do this for the other VM's and the second Physical server.
The Hyper-V manager no longer has time sync checked.
This use to work before I contacted Microsoft 2 weeks ago to help me with a replication issue. The PDC use to get the time from the "local clock" but now its from "time.microsoft x09. Im not sure if that's the problem? Does the CMOS battery affect this? Im running out of ideas and Microsoft will no longer help as they said we need to open a new ticket.
We have 2 Physical Servers
1 Physical Server running WinServer2008 Standard R2 which is the PDC, DNS DHCP and with the Hyper-V role installed running 3 VM's
3 VM's (The second DC, File Server and a Finance Server)
The Other physical server is running Windows Storage Server 2008 R2 (This is where we back up our images to)
Ok so i did Net Time \\The-PDC-Server /set /y and everything synced perfectly and after a while All Vm's and the other Physical server were off again by a few seconds. Now this morning I see the logs below on the VM's and the other Physical server but nothing on the PDC Physical server.
VM File Server:
Event ID 50 9/2/2015 1:26:42AM
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
Event ID 24 9/2/2015 5:43:06AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize.
Event ID 29 9/2/2015 5:43:06AM
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
Event ID 37 9/2/2015 5:58:06AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
VM Finance Server
Event ID 24 9/2/2015 6:40:44AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Event ID 37 9/2/2015 6:55:45AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
VM Second DC Server
Event ID 24 9/2/2015 4:50:43AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Event ID 37 9/2/2015 5:05:44AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
Event ID 24 9/2/2015 6:39:35AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Event ID 37 9/2/2015 8:00:24AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
Event ID 24 9/2/2015 9:25:57AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.
Physical Windows Storage Server 2008 R2
Event ID 24 9/2/2015 5:36:53AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization.
Event ID 37 9/2/2015 7:00:17AM
The time provider NtpClient is currently receiving valid time data from MYPDCSERVER (ntp.d|IPof VM->IPofPDC).
Event ID 24 9/2/2015 8:25:46AM
Time Provider NtpClient: No valid response has been received from domain controller MYPDCSERVER after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization.
So for me to fix this and get all the errors away for a while I tried to go to my second DC VM since I was on it at the time and ran
w32tm /resync
I get a response saying could not access contact time source something of the sort. So to fix this I logged into the Physical PDC server and ran
w32tm /resync
Once the output was successful I was able to go back to the second DC VM and ran
w32tm /resync
with sucess and than followed by
w32tm /query /status (Shows the times source of the PDC)
net time (Shows the PDC).
I do this for the other VM's and the second Physical server.
The Hyper-V manager no longer has time sync checked.
This use to work before I contacted Microsoft 2 weeks ago to help me with a replication issue. The PDC use to get the time from the "local clock" but now its from "time.microsoft x09. Im not sure if that's the problem? Does the CMOS battery affect this? Im running out of ideas and Microsoft will no longer help as they said we need to open a new ticket.
Yes the CMOS clock can mess with things--check to make sure it is right and that you have a good battery. I have never been a fan of using MS time--I use this chart to pick my time server, I suggest you choose one that is closest to you http://tf.nist.gov/tf-cgi/servers.cgi. That been said the event log errors you have shown me may also point to the possibility of issues with your network--you may have a bad network card and/or network switch/router and/or you may be having power surges (Losing electricity). I would check all those too in addition to changing your time server.
ASKER
Whats the best way to test if I have a bad bad network card and/or network switch/router and/or you may be having power surges (Losing electricity).
Regarding the power surges. The servers are connected to two UPS's and those UPS's are connected to emergency power. Meaning if the building loses power the generators turn on and the servers and all equipment in my IT should not go down.
Regarding the power surges. The servers are connected to two UPS's and those UPS's are connected to emergency power. Meaning if the building loses power the generators turn on and the servers and all equipment in my IT should not go down.
ASKER
i just did this on the PDC
w32tm /config /manualpeerlist:”us.pool.n
net stop w32time
net start w32time
I ran w32tm /query /status
the source says CMOS clock
thats not right
w32tm /config /manualpeerlist:”us.pool.n
net stop w32time
net start w32time
I ran w32tm /query /status
the source says CMOS clock
thats not right
ASKER
Ok I ran it again I guess it took time for it to update. This is from the PDC
C:\Windows\system32>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.1482001s
Root Dispersion: 0.4474028s
ReferenceId: 0x6BAAE008 (source IP:)
Last Successful Sync Time: 9/2/2015 11:35:24 AM
Source: us.pool.ntp.org
Poll Interval: 8 (256s)
I checked my registry
HKEY_LOCAL_MACHINE\SYSTEM\
Default REG_SZ (value not set)
NtpServer REG_SZ us.pool.ntp.org
ServiceDll REG_EXPAND_SZ %systemroot%\system32\w32t
ServiceDLLUnloadOnStop REG_DWORD 0x00000001 (1)
ServiceMain REG_SZ SvchostEntry_W32Time
Type REG_SZ NTP
How does this look to you?
C:\Windows\system32>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.1482001s
Root Dispersion: 0.4474028s
ReferenceId: 0x6BAAE008 (source IP:)
Last Successful Sync Time: 9/2/2015 11:35:24 AM
Source: us.pool.ntp.org
Poll Interval: 8 (256s)
I checked my registry
HKEY_LOCAL_MACHINE\SYSTEM\
Default REG_SZ (value not set)
NtpServer REG_SZ us.pool.ntp.org
ServiceDll REG_EXPAND_SZ %systemroot%\system32\w32t
ServiceDLLUnloadOnStop REG_DWORD 0x00000001 (1)
ServiceMain REG_SZ SvchostEntry_W32Time
Type REG_SZ NTP
How does this look to you?
That's good. Are the other systems keeping time. Only way to test network card is with hardware testing software like what came with your server. On your switch I would move the cables to different ports to see if the ports are going bad. On the switch I assume it is plugged into a UPS too--you can test if it is working by unplugging it and see if it maintains power or you can use the self test option that most come with.
ASKER
Ok so things have calmed down a bit.
The constant errors and warnings from the Server 2003 VM have gone away completely. This VM i guess when it was setup the admin synced the time with one of the Microsoft time pools. I know this because i ran the net time /querysntp and it said time.microsoft something of that sort.
The other two VM's
1) Second DC VM. I see time warnings no errors at least once or twice a day. At times there are no warnings or errors. Warnings appear for example at 1050AM the same warning appears on the Finance VM at the same time
2) Finance VM. I see time warnings no errors at least once or twice a day. At times there are no warnings or errors.
I run w32tm /query /status and both receive the time from the physical server which is the PDC.
All 3 VM's 2003, and both 2008 they are ahead by 5-6 seconds of the PDC and at times they are synced perfectly.
The PDC receives its time source from us.pool.ntp.org
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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.1316781s
Root Dispersion: 0.1204470s
ReferenceId: (source IP: XXXX)
Last Successful Sync Time: 9/23/2015 1:49:34 PM
Source: us.pool.ntp.org
Poll Interval: 6 (64s)
By using the us.pool.ntp.org source rather than the microsoft one. A lot go the warnings and errors went away and I only see what I described above. Is this normal? should I be worried
The constant errors and warnings from the Server 2003 VM have gone away completely. This VM i guess when it was setup the admin synced the time with one of the Microsoft time pools. I know this because i ran the net time /querysntp and it said time.microsoft something of that sort.
The other two VM's
1) Second DC VM. I see time warnings no errors at least once or twice a day. At times there are no warnings or errors. Warnings appear for example at 1050AM the same warning appears on the Finance VM at the same time
2) Finance VM. I see time warnings no errors at least once or twice a day. At times there are no warnings or errors.
I run w32tm /query /status and both receive the time from the physical server which is the PDC.
All 3 VM's 2003, and both 2008 they are ahead by 5-6 seconds of the PDC and at times they are synced perfectly.
The PDC receives its time source from us.pool.ntp.org
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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.1316781s
Root Dispersion: 0.1204470s
ReferenceId: (source IP: XXXX)
Last Successful Sync Time: 9/23/2015 1:49:34 PM
Source: us.pool.ntp.org
Poll Interval: 6 (64s)
By using the us.pool.ntp.org source rather than the microsoft one. A lot go the warnings and errors went away and I only see what I described above. Is this normal? should I be worried
time should be exact but sometimes they may be slightly off. Whether in your case 5-6 seconds is too much only you can decide. I do have one customer, a bank, that needs it to be exact and I had to install a 3rd party solution that constantly checks and updates time. You have to decide if 5-6 seconds is an issue of if you can live with it.
ASKER
I can live with it. I do not have time sensitive applications. Just wanted to see if being off a couple of seconds is something normal.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You were a great help thank you