w32Time - External Source Sinc - HELP!!

Hi! I've folowed (step by step) this MS Article to configure my forest root domain controller to sync with an external source: http://support.microsoft.com/?scid=kb%3Ben-us%3B816042&x=8&y=12
Mi DC is a VPC hosted on Virtual Server 2005 R2.

I've tried both configurations:
* Configure the W32time service to send symmetric active mode packets and (by editing the registry)
* to send client mode packets to my NTP server list (by using "w32tm /config /manualpeerlist:peers /syncfromflags:manual" )
Anyway I'm getting the following Events:


Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 12/07/2006
Time: 05:51:02 a.m.
User: N/A
Computer: PDC
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 240 minutes. NtpClient has no source of accurate time.

<<One for each external source configured>>
===============================
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: 12/07/2006
Time: 05:51:02 a.m.
User: N/A
Computer: PDC
Description:
Time Provider NtpClient: No valid response has been received from manually configured peer tick.nap.com.ar,0x1 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.

<<One for each external source configured>>
==============================
Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Date: 12/07/2006
Time: 04:36:01 a.m.
User: N/A
Computer: PDC
Description:
The time provider NtpClient cannot reach or is currently receiving invalid time data from tick.nap.com.ar (ntp.m|0x1|10.1.0.12:123->200.10.140.2:123).



The Hotfix Q830092 does not apply to my server since its a Windows 2003 Server EE R2 (wich already includes a newer version of the w32time.dll included shiiped with the Q830092).
I've tested all the selected NTP Servers and are fully functional, so I've turned on w32tm.dll debugging, getting this dump for each time it tries to get a timestamp from the listed NTP Servers.


Polling peer 216.244.192.3 (ntp.m|0x0|10.1.0.12:123->216.244.192.3:123)
Sending packet to 216.244.192.3 (ntp.m|0x0|10.1.0.12:123->216.244.192.3:123) in Win2K detect mode, stage 1.
No response from peer 216.244.192.3 (ntp.m|0x0|10.1.0.12:123->216.244.192.3:123).
5 Age:5 Ofs:+00.0000000s...
4 Age:4 Ofs:+00.0000000s...
3 Age:3 Ofs:+00.0000000s...
2 Age:2 Ofs:+00.0000000s...
1 Age:1 Ofs:+00.0000000s...
0 Age:0 Ofs:+00.0000000s...
Logging information: NtpClient cannot reach or is currently receiving invalid time data from 216.244.192.3 (ntp.m|0x0|10.1.0.12:123->216.244.192.3:123).
Peer poll: Max:32.0000000s Cur:00.0000000s
PeerPollingThread: waiting 31.970s


I'ts driving me crazy since I've tried every article found on the web and still cannot find what my issue.
Any (I mean ANY) help will be appreciated!!
Thanks a lot!!

Beto.



Relevant Pages

  • Re: Time Service in Windows XP
    ... What is the best practise to configure the W32Time Service on a laptop with windows xp? ... When the Laptop is conected to the domain, then it will get the time from the time server. ... The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. ... It polls a subset of servers. ...
    (microsoft.public.windowsxp.general)
  • w32time root delay / root dispersion error
    ... We have a little problem concerning w32time. ... network of computers, where every computer should have same time. ... synchronization should be done by using NTP protocol. ... * level A servers synchronize their time from external time sources. ...
    (microsoft.public.windows.server.general)
  • Re: can i use w32time to syncronise in a non domain scenario - windows2003
    ... I suspect you will not be able to use w32time on servers which are ... that situation and use the domain time heirarchy. ... server in a domain which will actually use a configured time source ...
    (comp.protocols.time.ntp)
  • Re: W32TIME errors in event viewer
    ... If your servers are not picking up a DHCP lease then w32time errors will ... > I found in the servers is that they all have W32TIME event ...
    (microsoft.public.windows.server.general)
  • Re: Time server?
    ... Event Type: Warning ... Event Source: W32Time ... Computer: VOLE ... Time Provider NtpClient: No valid response has been received from manually ...
    (microsoft.public.windows.server.sbs)
Loading