Windows 2003 display time source

Should it? I just noticed this is Event Viewer. Even though the registry settings above would indicate the PDCe is configured with a time source, I get the following:. Description: The time service has not synchronized the system time for seconds because none of the time service providers provided a usable time stamp. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock.

Monitor the system events displayed in the Event Viewer to make sure that a more serious problem does not exist. NtpServer cannot provide secure signed time to the client and will ignore the request.

The error was: Not enough storage is available to process this command. Occassionally the above message also end with "the specified user does not exist" or ". The change is scheduled to be done next week so I'm hoping to get things as much in line as possible before then.

So what are these That means your PDCE is not getting tim from external at all. Secondly, if those I am only at this client on a limited basis so I don't have a lot of details but it is my understanding that those two servers -the I have asked them to verify that UDP port is open.

Those two servers are not technically external since they are obviously on the internal LAN but those servers do sync to an external source and are the servers they want to be the time servers for the PDC. Does it matter that they are not on an external network? In other words, as long as they are 'external' to the PDC and are truly reliable time servers, shouldn't that work just fine? Is there a way I can tell if those time servers are the 'right' sort of time servers? They obviously show up in the registry but are they giving the right sort of reply to the PDC?

I will be making this change today. Turns out the time source is a Cisco appliance. I believe it is a Cisco switch. I suspect the issue might be how this device and the Windows servers are communicating. I'll have to see what comes of it when I make the changes above, reset everything and try to resync things up. Upon further investigation, I find that this client has a setting in the Default Domain policy to apply sntp settings.

I originally looked for this in the default domain controller policy and didn't find it per article KB, then found it in the default policy. So, I will remove those settings and retry syncing the time again. Unfortunately this client has fairly strong change management requirements so it will probably be a week before I can perform the changes.

Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows Server General Forum. Try this doc. It is a bit old but still valid. I have one server that is off by 10 minutes. It is a VM. All my other servers are also VM's and don't seem affected. Have you tried clearing the ntp server and then setting it again?

What OS is it running? Are you running in a domain? Is your time source remote or local? We are running ESXi. I just checked and VM Tools was syncing time with the host so I unselected that but it is still showing the wrong Time. I even did a gpupdate and restarted the server hoping it would pull in the correct time.

It looks like Windows is outright lying to me about what source it is using for time and has some sort of internal conflict going on according to these results. My secondary DC was off by 10 minutes when I checked it.

Of course it is Server core so one has to actively check the time to even notice this issue. I had the same issue with our DC being off. Improve this question. Citizen 1, 1 1 gold badge 10 10 silver badges 19 19 bronze badges. Tim Alexander Tim Alexander 1, 5 5 gold badges 27 27 silver badges 39 39 bronze badges.

If it's domain, then not, apparently you need to start the service, and then configure for PDC, but if you have it on DC and reports OK, this should be all fine. Dumpreg always returns registry settings, but doesnt show if service is started or working. Would this override any sntp settings that may have been configured before? It just some of our members servers that I wanted to give the once over to. Well the time service has to be specifically configured via GPO to talk to the domain controller, or the best two domain controllers.

To have it well working, you need to configure it thru GPO, because defaults are very generic, and they very often drift a lot. Add a comment. Active Oldest Votes. Improve this answer.

Tim Brigham Tim Brigham On a test server it is showing as not configured which leads me to believe it is picking it up from the DC which is good. Alex Berry Alex Berry 2, 12 12 silver badges 23 23 bronze badges. That's not actually true. All domain members should get their time settings from a domain controller, but that doesn't mean they will, or that it can't be changed. Also, all machines will be getting their time from an NTP source