W32Time Error

[jhutton]

I currently getting the error and was looking for some input on how to trouble shoot it.

Thanks in advance,
Jim

The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 960 minutes. NtpClient has no source of accurate time.

 

[PHV]

Ask the help wizard for ntp

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[jhutton]

By help wizard do you the standard Help and Support search?

 

[PHV]

Yes.
You may also ask for ntpclient

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[jhutton]

I found an article that has my error listed but after I follow the suggested fix, I still get the same error.
I'm trying to use the internal CMOS. Why would it not allow it access.

Link:

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

Error:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 960 minutes. NtpClient has no source of accurate time.

 

[58sniper]

That's usually a problem with either the port not being open on the firewall, the time source not being available (unlikely), network congestion, or an improperly configured NTP source.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[TechSoEasyMVP]

I never use an internal clock for this, and always configure an SBS to use an external time source, then have the clients use the SBS for synchronization because system time is critical to your network functioning properly. (Kerberos requires everything to be within 5 minutes of eachother).

My guess is that if you're getting the error when W32Time is configure to use the CMOS clock that your CMOS battery may be dead or not seated properly.

Jeff
TechSoEasy