Event ID17/29

[offmyrocker]

Getting the following errors on Server03.

ID17
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'ntp.wa.westnet.com.au'. NtpClient will try the DNS lookup again in 15 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C)

ID29
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 15 minutes. NtpClient has no source of accurate time.

Anyone know how to resolve these issues?

 

[Lemon13]

it seems ur dns cant resolve the fqdn, did u setup a forward-lookup to ur isp-dns-server?

configure windows time

http://technet.microsoft.com/en-us/library/cc784929.aspx

M. Knorr

MCSE, MCTS, MCSA, CCNA

 

[offmyrocker]

I didnt set it up, but I think you are correct, someone before me configured it. Have you any suggestions to resolve the issue? That is an address from the isp.

 

[ITPangaeaArchitect]

what the id 17 event is telling you, is that the NTP functions are not functioning on the server configured as the time source (ntp.wa.westnet.com.au), as far as the system generating the errors can detect. It also goes on to tell you that the service couldnt be found in the namespace, which means it did resolve the name fine.

This is usually caused by port 123 being closed on a firewall on either side of the connection.

if this is a client machine, member server, or domain controller that is NOT the PDCe in a domain, then it should be utilizing the DC for windows time. You should be able to run "w32tm /config /syncfromflags:domhier /update" to reset the configuration for windows time back to the NT5DS algorithm to use the DC the client's secure channel is established with to sync time. You need to restart windows time service on the system after reconfiguration.
NOTE: net time /querysntp will typically show time.windows.com and not your DC..this is normal as it is a simple method for static settings checks only
If you want to set it staticly to a DC, you can, however, windows time will fail if that DC cannot be reached. You can do this by running net time /setsntp:dc.domain.com (where dc.domain.com = your domain controller FQDN, IP, or netbios name)


if this is the PDCe:

go to

http://tycho.usno.navy.mil/ntp.html

and identify a NTP server within the same time zone you are in (link covers US only)
run net time /setsntp:<public NTP server name>

that should fix you up, assuming that 123 is opened on your firewall to allow for ntp requests.


- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (

http://it-pangaea.com)