time.windows.com

From: Ninon Chassé (nchasse33_at_NoSpamhotmail.com)
Date: 09/18/04 

Date: Fri, 17 Sep 2004 22:18:22 -0400

Hello,

Every time I tried to synchronize my PDC running Windows 2003 server or
Windows XP SP1 workstation (my home pc) with time.windows.com, I get errors.
On the server side I get an event that says "No response has been received
from Manual peer time.windows.com..." while on the workstation I get "An
error occurred while Windows was synchronizing with time.windows.com".

I opened my firewall port and configured the PDC using the following
commands, thanks to the help of Mike aka Miha Pihler:
w32tm /config /syncfromflags:manual /manualpeerlist:<PeerList>
w32tm /config /update

Where <PeerList> is a comma-separated list of DNS name time sources, or IP
addresses. In my case it was time.windows.com but couldn't contact it. I
even try to Ping it but received Request Timed Out... Consequently I've
decided to contact a local (Canadian) SNTP Stratum-1 provider and then
installed the following hotfix:

W32Time frequently logs Event ID 50 and poor time synchronization occurs on
Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;830092&sd=ee

The problem with the PDC seems to be under control now but still cannot
understand why time.windows.com cannot be contacted! I wasn't even sure
that server ACTUALLY existed or if it's too busy or restricted for US use
only!!! Anyone knows?

My home computer still cannot synchronized with Microsoft :-(

P.S. Sorry Rebecca; I totally understand! 

-- 
Ninon

Relevant Pages

  • Re: w32Time
    ... I have two Server choices: ... Automatically synchronize.. ... Internet time server. ... MS-MVP Windows Shell/User ...
    (microsoft.public.windowsxp.basics)
  • Re: Upgrading from NT 4.0 to 2000 server
    ... > your windows 2000 member server up as a backup domain controller, ... In NT 4.0 the NT 4.0 PDC is the only DC that carries a writeable copy of the ... SAM, You MUST upgrade the existing NT 4.0 PDC to AD first in order to carry ... How to Upgrade Windows NT Server Version 4.0 to Windows 2000 ...
    (microsoft.public.win2000.general)
  • Re: NT4 > Win 2003 Server
    ... When two different Windows NT Advanced Servers or Windows NT Servers in a ... I think the most convenient upgrade solution is install Windows NT BDC on ... the new server, promote it to PDC and then inplace-upgrade it to Windows ...
    (microsoft.public.windows.server.migration)
  • RE: NT4 to Server 2003 Migration
    ... Windows 2003 but the new hardware will not support Windows NT 4.0. ... It will only be used as a transition server. ... | functions, too), 1 PDC, and a few member ...
    (microsoft.public.windows.server.migration)
  • Re: Upgrading to 2003 from NT
    ... The new computer cannot run Windows NT, so if I install 2003 on the new ... Then, once that is done, we also have an Exchange 5.5 server. ... >> get the PDC and BDC to recognize the new computer as the DC? ... > With AD correctly configured DNS is a must. ...
    (microsoft.public.windows.server.general)
Quantcast