Time Sync - 15 minutes offset

  • Thread starter Thread starter FB
  • Start date Start date
F

FB

Guest
I have 180 PCs and i run a Script with NET TIME to check the time sync and
for my surprise there is 15 minutes difference (see distribution table below)

The Script runs in 3 minutes and i´m puzzled because AD is working fine but
there is a Default Domain Policy for block Logins when clocks are not
synchronized (5 minutes?!)


I´ve followed the article and my PC have a 3 minutes difference between my
PC clock and Atomic CLock

http://support.microsoft.com/kb/816042
How to configure an authoritative time server in Windows Server 2003

Distribution Table

TIME - Ammount
09:27 1
09:28 4
09:29 4
09:30 10
09:31 7
09:32 9
09:33 11
09:34 11
09:35 6
09:36 6
09:37 26
09:38 38
09:39 41
09:40 7
09:44 1
 
Re: Time Sync - 15 minutes offset

Hello FB,

The atomic clock is a internet time server or a hardware modul in your server?
If it is an internet time server use this way:

PDCEmulator:

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/


Client configuration:
To configure a client computer for automatic domain time synchronization

w32tm /config /syncfromflags:domhier /update

After that run:

net stop w32time

net start w32time

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

> I have 180 PCs and i run a Script with NET TIME to check the time sync
> and for my surprise there is 15 minutes difference (see distribution
> table below)
>
> The Script runs in 3 minutes and i´m puzzled because AD is working
> fine but there is a Default Domain Policy for block Logins when clocks
> are not synchronized (5 minutes?!)
>
> I´ve followed the article and my PC have a 3 minutes difference
> between my PC clock and Atomic CLock
>
> http://support.microsoft.com/kb/816042 How to configure an
> authoritative time server in Windows Server 2003
>
> Distribution Table
>
> TIME - Ammount
> 09:27 1
> 09:28 4
> 09:29 4
> 09:30 10
> 09:31 7
> 09:32 9
> 09:33 11
> 09:34 11
> 09:35 6
> 09:36 6
> 09:37 26
> 09:38 38
> 09:39 41
> 09:40 7
> 09:44 1
 
Re: Time Sync - 15 minutes offset


The Atomic Clock is provided by a .GOV.BR institution (tips on NTP.BR)

I´ll try your suggestion, but why the MS KB Article is not a good procedure?



"Meinolf Weber" wrote:

> Hello FB,
>
> The atomic clock is a internet time server or a hardware modul in your server?
> If it is an internet time server use this way:
>
> PDCEmulator:
>
> 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/
>
>
> Client configuration:
> To configure a client computer for automatic domain time synchronization
>
> w32tm /config /syncfromflags:domhier /update
>
> After that run:
>
> net stop w32time
>
> net start w32time
>
> 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
>
> > I have 180 PCs and i run a Script with NET TIME to check the time sync
> > and for my surprise there is 15 minutes difference (see distribution
> > table below)
> >
> > The Script runs in 3 minutes and i´m puzzled because AD is working
> > fine but there is a Default Domain Policy for block Logins when clocks
> > are not synchronized (5 minutes?!)
> >
> > I´ve followed the article and my PC have a 3 minutes difference
> > between my PC clock and Atomic CLock
> >
> > http://support.microsoft.com/kb/816042 How to configure an
> > authoritative time server in Windows Server 2003
> >
> > Distribution Table
> >
> > TIME - Ammount
> > 09:27 1
> > 09:28 4
> > 09:29 4
> > 09:30 10
> > 09:31 7
> > 09:32 9
> > 09:33 11
> > 09:34 11
> > 09:35 6
> > 09:36 6
> > 09:37 26
> > 09:38 38
> > 09:39 41
> > 09:40 7
> > 09:44 1
>
>
>
 
Re: Time Sync - 15 minutes offset


The Server Command returned an error in the "/reliable:yes " parameter

"Meinolf Weber" wrote:

> Hello FB,
>
> The atomic clock is a internet time server or a hardware modul in your server?
> If it is an internet time server use this way:
>
> PDCEmulator:
>
> 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/
>
>
> Client configuration:
> To configure a client computer for automatic domain time synchronization
>
> w32tm /config /syncfromflags:domhier /update
>
> After that run:
>
> net stop w32time
>
> net start w32time
>
> 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
>
> > I have 180 PCs and i run a Script with NET TIME to check the time sync
> > and for my surprise there is 15 minutes difference (see distribution
> > table below)
> >
> > The Script runs in 3 minutes and i´m puzzled because AD is working
> > fine but there is a Default Domain Policy for block Logins when clocks
> > are not synchronized (5 minutes?!)
> >
> > I´ve followed the article and my PC have a 3 minutes difference
> > between my PC clock and Atomic CLock
> >
> > http://support.microsoft.com/kb/816042 How to configure an
> > authoritative time server in Windows Server 2003
> >
> > Distribution Table
> >
> > TIME - Ammount
> > 09:27 1
> > 09:28 4
> > 09:29 4
> > 09:30 10
> > 09:31 7
> > 09:32 9
> > 09:33 11
> > 09:34 11
> > 09:35 6
> > 09:36 6
> > 09:37 26
> > 09:38 38
> > 09:39 41
> > 09:40 7
> > 09:44 1
>
>
>
 
Re: Time Sync - 15 minutes offset

Hello FB,

It is more complicated from my point of view to change all the registry keys.
It is not a bad solution, just another one.

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

> The Atomic Clock is provided by a .GOV.BR institution (tips on NTP.BR)
>
> I´ll try your suggestion, but why the MS KB Article is not a good
> procedure?
>
> "Meinolf Weber" wrote:
>
>> Hello FB,
>>
>> The atomic clock is a internet time server or a hardware modul in
>> your server? If it is an internet time server use this way:
>>
>> PDCEmulator:
>>
>> 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/
>> Client configuration:
>> To configure a client computer for automatic domain time
>> synchronization
>> w32tm /config /syncfromflags:domhier /update
>>
>> After that run:
>>
>> net stop w32time
>>
>> net start w32time
>>
>> 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
>>> I have 180 PCs and i run a Script with NET TIME to check the time
>>> sync and for my surprise there is 15 minutes difference (see
>>> distribution table below)
>>>
>>> The Script runs in 3 minutes and i´m puzzled because AD is working
>>> fine but there is a Default Domain Policy for block Logins when
>>> clocks are not synchronized (5 minutes?!)
>>>
>>> I´ve followed the article and my PC have a 3 minutes difference
>>> between my PC clock and Atomic CLock
>>>
>>> http://support.microsoft.com/kb/816042 How to configure an
>>> authoritative time server in Windows Server 2003
>>>
>>> Distribution Table
>>>
>>> TIME - Ammount
>>> 09:27 1
>>> 09:28 4
>>> 09:29 4
>>> 09:30 10
>>> 09:31 7
>>> 09:32 9
>>> 09:33 11
>>> 09:34 11
>>> 09:35 6
>>> 09:36 6
>>> 09:37 26
>>> 09:38 38
>>> 09:39 41
>>> 09:40 7
>>> 09:44 1
 
Re: Time Sync - 15 minutes offset


Sorry! The command was typed on XP Local machine
(-:

It worked!



"Meinolf Weber" wrote:

> Hello FB,
>
> The atomic clock is a internet time server or a hardware modul in your server?
> If it is an internet time server use this way:
>
> PDCEmulator:
>
> 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/
>
>
> Client configuration:
> To configure a client computer for automatic domain time synchronization
>
> w32tm /config /syncfromflags:domhier /update
>
> After that run:
>
> net stop w32time
>
> net start w32time
>
> 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
>
> > I have 180 PCs and i run a Script with NET TIME to check the time sync
> > and for my surprise there is 15 minutes difference (see distribution
> > table below)
> >
> > The Script runs in 3 minutes and i´m puzzled because AD is working
> > fine but there is a Default Domain Policy for block Logins when clocks
> > are not synchronized (5 minutes?!)
> >
> > I´ve followed the article and my PC have a 3 minutes difference
> > between my PC clock and Atomic CLock
> >
> > http://support.microsoft.com/kb/816042 How to configure an
> > authoritative time server in Windows Server 2003
> >
> > Distribution Table
> >
> > TIME - Ammount
> > 09:27 1
> > 09:28 4
> > 09:29 4
> > 09:30 10
> > 09:31 7
> > 09:32 9
> > 09:33 11
> > 09:34 11
> > 09:35 6
> > 09:36 6
> > 09:37 26
> > 09:38 38
> > 09:39 41
> > 09:40 7
> > 09:44 1
>
>
>
 
Re: Time Sync - 15 minutes offset

Hello FB,

Nice to hear that it works.

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

> Sorry! The command was typed on XP Local machine
> (-:
> It worked!
>
> "Meinolf Weber" wrote:
>
>> Hello FB,
>>
>> The atomic clock is a internet time server or a hardware modul in
>> your server? If it is an internet time server use this way:
>>
>> PDCEmulator:
>>
>> 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/
>> Client configuration:
>> To configure a client computer for automatic domain time
>> synchronization
>> w32tm /config /syncfromflags:domhier /update
>>
>> After that run:
>>
>> net stop w32time
>>
>> net start w32time
>>
>> 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
>>> I have 180 PCs and i run a Script with NET TIME to check the time
>>> sync and for my surprise there is 15 minutes difference (see
>>> distribution table below)
>>>
>>> The Script runs in 3 minutes and i´m puzzled because AD is working
>>> fine but there is a Default Domain Policy for block Logins when
>>> clocks are not synchronized (5 minutes?!)
>>>
>>> I´ve followed the article and my PC have a 3 minutes difference
>>> between my PC clock and Atomic CLock
>>>
>>> http://support.microsoft.com/kb/816042 How to configure an
>>> authoritative time server in Windows Server 2003
>>>
>>> Distribution Table
>>>
>>> TIME - Ammount
>>> 09:27 1
>>> 09:28 4
>>> 09:29 4
>>> 09:30 10
>>> 09:31 7
>>> 09:32 9
>>> 09:33 11
>>> 09:34 11
>>> 09:35 6
>>> 09:36 6
>>> 09:37 26
>>> 09:38 38
>>> 09:39 41
>>> 09:40 7
>>> 09:44 1
 
Back
Top