event ids 29, 38, 47 for the w32 time service

hi guys and as always thanks for your time and expertise.  
for some reason, m pdc is no longer contacting the external time source i have configured.  my event log is now cluttered with the events i listed in the heading.
my time source is 192.5.41.41 or tock.usno.navy.mil.  for what it's worth, i can't ping these guys either.
this has worked seamlessly until the past four days.  Not sure what is going on so your advice, recommendations are greatly appreciated.
pendal1IT ManagerAsked:
Who is Participating?
 
Hypercat (Deb)Commented:
Could be many reasons that this server isn't responding - including maintenance being done on their end, DNS changes, etc.  I would try simply changing the time server setting and see if you can use a different external source successfully.  It's easy to change the external time source setting from the command prompt:
net stop w32time
net time /setsntp: [servername or IP],0x8  (i.e., substitute tick.usno.navy.mil, time-a.nist.gov, or other external time source)
net start w32time
Immediately checking your event log will tell you if you've been able to connect to the new time server.
0
 
pendal1IT ManagerAuthor Commented:
hypercat, thanks for hte reply.  I just want to make sure you have all of the info in case it's relevant - Our PDC has win2003 installed.  If memory serves, I set this extermal time server up in the registry.  Is running your command enough or do I have to change my registry pararmeters?  Sorry for the delay in posting - I've been kind of running around.  Thanks.
0
 
pendal1IT ManagerAuthor Commented:
Thanks.  Something must be going on with tock.usno.navy.mil (192.5.41.41) because you can't ping it or anything.  As I indicated, it was working up until a few days ago.  However, your listed time server seems to be available and your command helped make the change quickly.  Your help is much appreciated.  
0
 
Hypercat (Deb)Commented:
Glad you got it working! As you may have already figured out, the answer to your question is that the command changes the setting in the registry, so it will continue to use the new time server setting until/unless you change it again.
0
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.

All Courses

From novice to tech pro — start learning today.