w32time event errors - should I worry?

[tookawhile]

I keep getting w32time errros in the event log, #11, NTP server didn't respond.

I have SP4 installed which I believe fixes the bug in w32time for rollover queries.

I can query sntp and get back the 4 IP numbers which I use for time services. I know you are but to use URLs but because of the bug I setup using IP numbers.

When I check the time against the speaking clock it seems to absolutely spot on to the second.

I can ping the IP# - so should I worry about the errors?

 

[tookawhile]

...and port 123 is open.

 

[Seaspray0]

If it is the server, I wouldn't be too concerned with the time event error. You will only have difficulty if the PC's become more than 5 minutes off of each other. The clients should be synchronizing their clocks to the server but the server is not finding the time server to synchronize itself to. You can use dos commands to specify a different NTP server on the internet if you have trouble with the one you are attemting to contact.

Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA

 

[tookawhile]

The time server I'm using (1st one) is time-nw.nist.gov so it is reliable - I hope.

This still doesn't explain why I keep getting error logs.

I would like ntp time to be rock solid.

 

[muddyfox1009]

if you run any replication, then the servers shouldn't really be out of sync. if not, you wont have 2 worry.

 

[porkchopexpress]

If your DC's drift more than 5 mins out you will start to have issues with authentication and replication.

If however the issue is that your PDCe (usually the master time server) cannot connect to an external time source then the Windows time service will still keep your workstations and servers in sync internally so you won't observe any problems.

You know what Jack Burton always says at a time like this...