topic Re: NTP client configuration on Windows 2003 Server in Windows Server 2003

NTP client configuration on Windows 2003 Server

Igor Sovin — Wed, 18 Oct 2006 01:26:26 GMT

Hi !

I want to set my Windows 2003 Server as NTP client.
NTP server is configured on HP-UX machine.
How to configure Windows machine to get time from the machine running HP-UX ?

Re: NTP client configuration on Windows 2003 Server

Igor Karasik — Wed, 18 Oct 2006 02:14:58 GMT

Igor,
Try
net time /setsntp:

Also, check that W32time service (windows time) on windows 2003 is started

You can see
http://www.microsoft.com/technet/itsolutions/cits/interopmigration/unix/usecdirw/21wsdsu.mspx
as well

Re: NTP client configuration on Windows 2003 Server

Igor Sovin — Wed, 18 Oct 2006 03:17:00 GMT

I did so.
It doesnt syncronize, although I see my hp-ux server in the output of

/querysntp

Re: NTP client configuration on Windows 2003 Server

Igor Karasik — Wed, 18 Oct 2006 03:27:38 GMT

>>It doesnt syncronize

Any related errors in Windows event viewer ?
w32tm service started ?
w32tm /monitor output ?

Re: NTP client configuration on Windows 2003 Server

Igor Sovin — Wed, 18 Oct 2006 03:34:40 GMT

w32tm started.

w32tm /monitor

Getting DC list for default domain...

Analyzing: 1 -- (0 of 2)

resolving referer 192.168.255.254 (1 of 2)...

resolving referer 192.168.255.254 (2 of 2)...

lyra.snos.ru *** PDC *** [10.1.32.1]:
ICMP: 6ms delay.
NTP: +0.0000000s offset from lyra.snos.ru
RefID: core2.mgmt.snos.ru [192.168.255.254]
leo.snos.ru [10.1.32.2]:
ICMP: 0ms delay.
NTP: +0.0004670s offset from lyra.snos.ru
RefID: core2.mgmt.snos.ru [192.168.255.254]

But the output doesnt contain the hp-ux server taht I want to syncronize with.

Last warnig in event Log was:

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: 18.10.2006
Time: 13:39:22
User: N/A
Computer: NICK
Description:
Time Provider NtpClient: No valid response has been received from manually configured peer sirius after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name.

And when there is an error:

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 18.10.2006
Time: 13:39:22
User: N/A
Computer: NICK
Description:
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.

Re: NTP client configuration on Windows 2003 Server

Ivan Ferreira — Wed, 18 Oct 2006 08:17:49 GMT

There are some values that you have to edit in the registry in order to use Unix as NTP server, please see:

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

Sync with the navy time server with "w32tm -s".

If you get a response that looks something like "RPC to local server returned 0x6b5", then it worked, but if you get "RPC to local server returned 0x0" then it did not, which usually happens if you run the command while the w32time service is running."

If you find a solution in this answer, please remember to thank with points.

Cheers.

Re: NTP client configuration on Windows 2003 Server

Igor Sovin — Thu, 19 Oct 2006 00:11:36 GMT

Hi Ivan!
I think that microsoft note provided helped me to solve my problem, but /s option in w32tm doesnt work.
I cant check if there is a syncronization process between windows machine and HP-UX server.

Re: NTP client configuration on Windows 2003 Server

Ivan Ferreira — Thu, 19 Oct 2006 09:02:34 GMT

You are right, the w32tm -s is for windows 2000, for 2003 is w32tm /resync.

If you stop and start the w32time service you should see and even entry in the system log like this:

The time provider NtpClient is currently receiving valid time data from server (ntp.m|0x0|192.168.0.1:123->192.168.0.2:123).

Re: NTP client configuration on Windows 2003 Server

Igor Sovin — Thu, 19 Oct 2006 21:49:36 GMT

It looks like sycronization doesnt work, although I see IP address of Windows machine in "ntpq -p" of my hp-ux time server.

There are w32time errors in Windows Event log.

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 34
Date: 10/19/2006
Time: 11:29:01 AM
User: N/A
Computer: RICK
Description:
The time service has detected that the system time needs to be changed by -7186 seconds. The time service will not change the system time by more than -3600 seconds. Verify that your time and time zone are correct, and that the time source judy.snos.ru (ntp.m|0x1|10.1.1.78:123->10.1.1.61:123) is working properly.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Re: NTP client configuration on Windows 2003 Server

Igor Sovin — Thu, 19 Oct 2006 23:45:37 GMT

Finally I solved my problem.
According to error in Event Log I turned internal clock of Windows Server machine manualy and then did w32tm /resync. Now it works fine and i see informational message in System Log (..now receiving valid time data.. ) that Ivan told about.
Thanks guys!