W32TM not syncing to external time source - event id 50 - source W32TM -

I'm getting the below warning in my event log.  I'm using the host 'time.uh.edu' as an external time source.  I was using a different time server previously but I was receiving this error so I then started to use 'time.uh.edu' instead.  Now I'm getting this error when using this time source.  I'm running Windows 2003 server with sp1.  It's a DC and an Exchange server.  What do I need to change?

Event Type:      Warning
Event Source:      W32Time
Event Category:      None
Event ID:      50
Date:            4/21/2006
Time:            4:57:02 AM
User:            N/A
Computer:      DREXEL_3
Description:
The time service detected a time difference of greater than 128 milliseconds  for 90 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.  

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
gopher_49Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

jss1199Commented:
Hi gopher_49,

Have you reviewd http://support.microsoft.com/default.aspx?scid=kb;en-us;830092?  The actual hotfix is posted here - http://www.adminnotes.com/hotfix/2004/04/830092.zip

Cheers!

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
jss1199Commented:
gopher_49,


Actually, this hotfix was supposedly included in SP1.  I would check the file version and reapply if necessary.  Something may have replaced the w23time.dll to its pre-SP1 state
gopher_49Author Commented:
I changed my W32tm source server and it works.  I made it reference a different external server and it's working perfectly.

thanks.
gopher_49Author Commented:
The error came back, however, I re-started the W32TM service and it's sync'ed up again.
gopher_49Author Commented:
Do I need to open any ports on my firewall?  I would think that due to me making the request for the time sync via UDP protocol the firewall would allow the traffic upon request.
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 2003

From novice to tech pro — start learning today.