Windows Time sever error 50 on Server SP2

I have set my Windows Time Service to pull time from an outside source and it has been working correctly for months. Starting a few days ago whenever it polls the extrernal source (every two hours) the following error is entered in the event log:

The time service detected a time difference of greater than 1 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.

I have tried changing external time servers. When I do that it can succesfuly poll it the first time, but two hours later when it polls again the same error appears. Is there a wat to change the time difference tolerated to higher then 1 millisecond?
wally_llama1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Look over this article.  Also, there is a reigstry import that will configure your time source automatically for you if you want to try to see if this fixes your problem.

http://support.microsoft.com/kb/816042/

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23630502.html

http://support.microsoft.com/kb/830092
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
wally_llama1Author Commented:
Registry import solved problem; now I just to to find which setting it was that did it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.