NTP bug in Windows 2003 ??
Stefan Holland
we have upgraded our domain from Windows NT to Windows 2003 a few weeks ago.
Since then we are unable to sync our domain time with an NTP server on a
Unix system.
The same NTP server has been succesfully contacted by our NT DC before
and still can be used by a Windows 2000 member server (see Windows
2000.log).
The ntp client on the Windows 2003 Server somehow does not like the NTP
data (see Windows 2003.log). We have tried serveral NTP servers, but our
Windows 2003 server does not like any of them.
I would very much appreciate any hint what its problem could be or what
has been changed in the w32time service from Windows 2000 to Windows 2003.
Regards,
Stefan
Eric Shen [MSFT]
This issue may be caused as that in Windows Server 2003 PDC Emulator,
NtpServer/Enabled=1, it sends out request in Symmetric Active mode; while
in standalone, NtpServer/Enabled=0, it is Client mode. Therefore, we need
to set the PDC emulator to be in client mode. Please try:
In a command window run the following commands:
1. w32tm /config /manualpeerlist:146.37.127.199,0x8 /syncfromflags:MANUAL
2. net stop w32time
3. net start w32time
4. w32tm /resync.
Also, please make sure that your server is not connecting to the external
server over a proxy server. You can check the event log as well to see if
there is any clue from time service.
Please let me know if this solves this issue or if you need further
assistance. I look forward to hearing from you.
Regards,
Eric Shen
Product Support Services
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! - www.microsoft.com/security
Stefan Holland
you are right, the log is from a Windows 2003 Server which acts as a PDC
emulator. We have got the same errors on another Windows 2003 Server
which is not a PDC emulator.
I have tried the steps you suggested but the problem ist still there.
The Windows 2003 Server directly connects to the NTP server, I have also
installed a NTP server on a machine next to the Windows 2003 Server,
without any success.
In the event log W32time 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 134.155.51.118
(ntp.m|0x0|134.155.55.138:123->134.155.51.118:123).
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 134.155.51.118 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.
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.
As far as I understand the debug log the NTP responds to the Windows
2003 Server, so it does not seem to be a network problem.
We have tried several NTP servers, all can be can successfully queried
by Windows 2000 and Windows NT Time Services but not from Windows 2003
Server.
Thanks for your help,
Stefan
Eric Shen [MSFT]
Windows Server 2003 uses NTP running on UDP port 123. The Windows 2000
version of this service uses Simple Network Time Protocol (SNTP). SNTP also
runs on UDP port 123. In order to know if this is a communication problem
to the time server, please try to use other NTP server for synchronization.
Please check the following list of time servers on the Internet:
262680 A List of the Simple Network Time Protocol Time Servers That Are
http://support.microsoft.com/?id=262680
In order to further troubleshoot on this issue, please capture the MPS
report:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_DirSvc.EXE
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_DirSvc_Readme.txt
This report will collect the information required for our research. It will
also test if there is any problem in your domain and if that can cause time
synchronization failure. Please send the output to me at
eric...@microsoft.com for investigation.
Stefan Holland
I have tried several SNTP servers from the list you supplied, in the
W32time debug log I found:
47150 12:16:49.5820605s - Polling peer ntps1-0.cs.tu-berlin.de
(ntp.m|0x0|134.155.55.138:123->130.149.17.21:123)
147150 12:16:49.5820605s - No response from peer ntps1-0.cs.tu-berlin.de
(ntp.m|0x0|134.155.55.138:123->130.149.17.21:123).
The SNTP server is working correctly, I can succesfully query it with a
NTP client.
I have even tried time.windows.com with the same result.
When contacting an NTP server I get:
147151 03:01:09.5347294s - Response from peer 134.155.51.118
(ntp.m|0x0|134.155.55.138:123->134.155.51.118:123), ofs: -00.0083067s
147151 03:01:09.5347294s - W32TmServiceMain: resync req, reg too soon.
In the later case the Windows 2003 Server seems to receive an answer,
but does not accept it.
Regards,
Stefan Holland
Eric Shen [MSFT]
Thank you for your patience.
Could you help me collect some more information on this issue to
investigate further? We need a detailed w32time log and it is better to
capture the network traffics as well.
To generate a detailed log, please try:
1. Use Registry Editor: (regedit.exe) to set the following entries:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\FileLogN
ame
REGSZ
C:\w32time.log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\FileLogE
ntries
REGSZ
0-300
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\FileLogS
ize
REGDWORD
100000000
2. Update w32time config to make it pick up the changes.
w32tm /config /update
It is better to capture all the network traffics on this computer when it
performs w32time update. To capture network traffic, refer to:
148942 How to Capture Network Traffic with Network Monitor
http://support.microsoft.com/?id=148942
You can send the information you get to me for further troubleshooting.
Thank you for your cooperation and time. I look forward to hearing from you.
Stefan Holland
thank you. I just sent you the requested information.
Regards,
Stefan
Eric Shen [MSFT]
I am performing research on this issue to see if we can find the cause. I
checked the MPS report you attached. However, as this report is in German
and we are unable to read further, I would recommend you submit this to the
local Microsoft Support Service if this is urgent for you. Thus, you will
get dedicated support and this issue can be resolved efficiently.
Thank you for your information, time and understanding.
Stefan Holland
ok, thanks !
Regards,
Stefan