Windows 2003 Server cannot connect to NTP server
Stefan Holland
we have upgraded an Windows NT domain with Windows 2000 clients to a
Windows 2003 domain.
The Windows 2003 DC are not able to get NTP time data from an external
NTP Server. It says it did not get a valid time stamp.
The same NTP server has been successfully accessed by the W32time
service on the WIndows NT DC before. It was also possible to start a
LocalNTP Time Server on the Windows NT DC to supply time information to
the Windows 2000 clients by setting the LocalNTP flag in the registry.
This does not work on the Windows 2003 DC, it will not start a LocalNTP
server even when the registry flag is set.
I have found some postings reporting this problem, but no solution.
I do not think that it is a configuration problem, so please do not hint
me to the various W32time documentations.
I guess it is a Windows 2003 Server bug or some sort of security
enhancement feature, in the latter case I would like to know how to turn
it off.
Thanks,
Stefan
Steven Liu [MSFT]
I did not get such error.
Would you please try other time server?
262680 A List of the Simple Network Time Protocol Time Servers That Are
http://support.microsoft.com/?id=262680
Please also check the firewall. Disable it and let's see whether this works.
If they all do not work, would you please give me the detail error message
about the w32time in the Windows 2003 server?
I will continue to help you with the problem.
Thanks for using Microsoft News Group!
Sincerely,
Steven Liu
Microsoft Online Partner Support
MCSE 2000
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Stefan Holland
we have tried serveral different time servers, I can successfully
contact these servers with other NTP clients e.g. "netdate" from the
Windows 2003 Server, so I do not think it is a network problem. There is
no firewall between the Windows 2003 server and the NTP server. The
firewall in Windows 2003 server is not enabled.
The event log states:
Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Date: 14.10.2003
Time: 14:28:04
User: N/A
Computer: Walter
Description:
The time provider NtpClient cannot reach or is currently receiving
invalid time data from 207.46.l30.100
(ntp.m|0x0|134.155.55.138:123->207.46.130.100:123).
134.155.55.138 and 207.46.130.100 are both working NTP servers.
Later you find:
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: 14.10.2003
Time: 07:26:06
User: N/A
Computer: Walter
Description:
Time Provider NtpClient: No valid response has been received from
manually configured peer 207.46.130.100 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:
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 14.10.2003
Time: 07:26:06
User: N/A
Computer: Walter
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.
It seems that this problem has been reported previously, e.g.:
http://groups.google.de/groups?q=NTP+47+w32time&hl=de&lr=&ie=UTF-8&oe=UTF-8&selm=u99W%24JpVDHA.2040%40TK2MSFTNGP10.phx.gbl&rnum=2
Thanks for your help,
Stefan
Steven Liu [MSFT]
Let's perform the steps in the following article to turn on the debug
logging of the Windows Time Service.
816043 HOW TO: Turn On Debug Logging in the Windows Time Service
http://support.microsoft.com/?id=816043
Then, restart the computer and let it run for one day. Then, send the
C:\Windows\Debug\w32time.log to me.
You can use the WinZip or WinRAR to compress the log file and attach it in
the post or send to me directly at: ste...@microsoft.com.
Steven Liu [MSFT]
From the log file, we got the following error.
NtpClient has been configured to acquire time from one or more time
sources, however none of the sources are currently accessible and no
attempt to contact a source will be made for 15 minutes. NTPCLIENT HAS NO
SOURCE OF ACCURATE TIME.
It seems that the computer can't contact the time source server
successfully.
First, please make sure the time source server's IP address is correct.
And, please make sure the port 123 is opened on your firewall/router. The
port is used for the time service to sync time.
Please note, that the Windows Time Service on the PDC FSMO MUST NOT point
to itself.
The following article describes the time source server.
262680 A List of the Simple Network Time Protocol Time Servers That Are
http://support.microsoft.com/?id=262680
Thanks for using Microsoft News Group!