Windows Time - problems

Afternoon all,

My DC (windows 2003 R2) running the PDCe role couldn't sync with
time.windows.com and I've now got mismatched times on other servers.

After doing some checking I notice that under
HKLM\system\services\currentcoltrolset\w32time that some server have
time.windows.com,0x1 as the NtpServer - is thi sby deault, of has hapenned
since my issues? Should I correct this key?

My understanding is that devices sync with local DC, local DC syncs with
PDCe, PDCe syncs with external time source (in this instance
time.windows.com)

Hello Andrew,

If you have listed under the \parameters key the TYPE REG_SZ with NT5DS this
will mean the domain is used for time sync.

What if you choose another time source:
w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update

With "PEERS" you can set the time source, either DNS name (time.windows.com)
or an ip address from a reliable time source.

Here you can find some of them:
http://www.pool.ntp.org/

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Afternoon all,
>
> My DC (windows 2003 R2) running the PDCe role couldn't sync with
> time.windows.com and I've now got mismatched times on other servers.
>
> After doing some checking I notice that under
> HKLM\system\services\currentcoltrolset\w32time that some server have
> time.windows.com,0x1 as the NtpServer - is thi sby deault, of has
> hapenned since my issues? Should I correct this key?
>
> My understanding is that devices sync with local DC, local DC syncs
> with PDCe, PDCe syncs with external time source (in this instance
> time.windows.com)
>

Andrew Story wrote:
> My DC (windows 2003 R2) running the PDCe role couldn't sync with
> time.windows.com and I've now got mismatched times on other servers.

I have found that "time.windows.com" has been unreliable for me. I
usually switch to another NTP provider.



Grant. . . .

"Andrew Story" <andrewDOTstoryATjameswalkerDOTbiz> wrote in message news:%...
> Afternoon all,
>
> My DC (windows 2003 R2) running the PDCe role couldn't sync with
> time.windows.com and I've now got mismatched times on other servers.
>
> After doing some checking I notice that under
> HKLM\system\services\currentcoltrolset\w32time that some server have
> time.windows.com,0x1 as the NtpServer - is thi sby deault, of has hapenned
> since my issues? Should I correct this key?
>
> My understanding is that devices sync with local DC, local DC syncs with
> PDCe, PDCe syncs with external time source (in this instance
> time.windows.com)
>
>


Double check the reg entry with Meinolf's post. If it's set otherwise, it won't follow the hierarchy. Regarding time.windows.com, I haven't seen any problems with it, but I usually set it to 192.5.41.41, one of the US Navy time sources. If not in this local, you can use any closest time source you like, using the link Meinolf provided.

It could also be simply a firewall issue blocking UDP 123 to the PDCe.

I also have a blog on the time service. Take a read. It may be helpful to understand how it all works, and it's limitations.

Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/arc...ws-server.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.