REPOST: Gaining Time

  • Thread starter Thread starter C Hall
  • Start date Start date
C

C Hall

Hi everybody,

This is a repost from 7/1 (Gaining Time).

I've tried several other time servers, but I am still getting NTP server did
not respond and the time creeps up 15 minutes over actual time. I've tried
using IP addresses and FQDN. I've not found anything in the KB. I can reset
time by stopping/starting w32time. Any suggestions?
 
Thanks, I'll check this out.

ptwilliams said:
Are you allowing UDP 123 out through your firewall from the PDCe?

If not, you'll need to grant access from the PDCe role holder. Otherwise
Click to expand...
it wont be able to synchronise. Running w32tm -once -v (after stopping
w32time) will show you if you are able to synchronise time or not. If you
can, it will get the time; if you cannot, it will timeout.
 
I'm baaaack! The firewall is not blocking NTP traffic. I found a KB article
on logging options for w32time, so I'm going to make some changes to logging
and see what I get. Also, the white paper on Windows Time Service says that
w32time will only check the first time server (dns name or ip address) in
the list, which is why they say to only put one in there. I would think that
redundancy would be a good thing. Can anyone verify this?
 
I changed the time server to include only one external time server:
time.windows.com. I changed logging, so that when our time server
synchronizes with the external source, I get a log entry. I got an entry at
1:40 pm that states that time was synched with time.windows.com. I don't
think that really happened, as the time is still off. Looking at the white
paper, the time server is supposed to synchronize every 45 minutes until the
clocks have successfully synchronized 3 times. Since I've been writing this,
the time was correctly synchronized and in the Event Viewer, I also got an
NTP didn't respond error (Event ID: 11). So eventually, the time does get
corrected at the auth. time server, but somewhere in between getting updated
from the external clock, I'm losing about 927 seconds.
 
If you're losing that much time in such a short space of time there's
something wrong! Your BIOS battery perhaps?


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


I changed the time server to include only one external time server:
time.windows.com. I changed logging, so that when our time server
synchronizes with the external source, I get a log entry. I got an entry at
1:40 pm that states that time was synched with time.windows.com. I don't
think that really happened, as the time is still off. Looking at the white
paper, the time server is supposed to synchronize every 45 minutes until the
clocks have successfully synchronized 3 times. Since I've been writing this,
the time was correctly synchronized and in the Event Viewer, I also got an
NTP didn't respond error (Event ID: 11). So eventually, the time does get
corrected at the auth. time server, but somewhere in between getting updated
from the external clock, I'm losing about 927 seconds.
 
Wouldn't the BIOS battery get 'recharged' while the server is up? The server
is just under a year old--not that the battery couldn't die young! I'm going
to try to trace back when this first started happening and see if anything
was added or changed, then go from there. I'll post my findings.
 
I've ruled out the BIOS system clock as the culprit. It looks like this
first began May 21, very sporadically. I thought I was on to something--for
a while, I would always get a NETLOGON error at the same time (Dynamic
registration of one or more DNS records failed....)--but that stopped
happening as frequently.
 
Paul,

The oddest thing: the time problem seems to have corrected itself. It's been
running fine all day, which it would usually go astray once an hour or
so...weird.
 
Well, that's great news... ;-)

Let us know what happens


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


Paul,

The oddest thing: the time problem seems to have corrected itself. It's been
running fine all day, which it would usually go astray once an hour or
so...weird.
 
I guess I spoke too soon. Came in this morning and was having the same
problem, albeit not as frequent. I'm going to continue monitoring and will
post any changes/results.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Gaining time 6
The NTP server didn't respond 14
Time Service Sync (NTP) 1
w32time 1
Time Service Sync (NTP) 2
REPOST: Gaining time--solution! 1
problems with external time server 8
Computer Crashing 8

Back
Top