Configuring w32time

[drtduarte]

Hello friends,

I know that we have plenty of threads on the web about w32time, but after
spending more than 3 days trying all the solutions I can't make it work...
why this have to be so hard to config...

On the client pc XP station I get the error on the w32time log:
ListeningThread -- no NTP service running at 192.168.1.12:123

192.168.1.12 is the server

On the server I keep getting this results on the log:
W32TimeHandler called: SERVICE_CONTROL_INTERROGATE
W32TmServiceMain: timeout
W32TmServiceMain: waiting 64.000s

I assume that the problem is only on the server, for some reason not acting
as an NTP server.

Here you have my registry config:

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time
Nome da classe: <SEM CLASSE>
Hora da última escrita: 22-01-2009 - 9:42
Valor 0
Nome: Description
Tipo: REG_SZ
Dados: Gere a sincronização da data e da hora de todos clientes
e servidores na rede. Se este serviço parar, a sincronização de data e hora
deixará de estar disponível. Se este serviço estiver desactivado, não será
possível iniciar quaisquer serviços que dependam explicitamente dele.

Valor 1
Nome: DisplayName
Tipo: REG_SZ
Dados: Hora do Windows

Valor 2
Nome: ErrorControl
Tipo: REG_DWORD
Dados: 0x1

Valor 3
Nome: Group
Tipo: REG_SZ
Dados:

Valor 4
Nome: ImagePath
Tipo: REG_EXPAND_SZ
Dados: %SystemRoot%\System32\svchost.exe -k netsvcs

Valor 5
Nome: Objectname
Tipo: REG_SZ
Dados: LocalSystem

Valor 6
Nome: Start
Tipo: REG_DWORD
Dados: 0x2

Valor 7
Nome: Type
Tipo: REG_DWORD
Dados: 0x20

Valor 8
Nome: FailureActions
Tipo: REG_BINARY
Dados:
00000000 05 00 00 00 00 00 00 00 - 00 00 00 00 02 00 00 00 ................

00000010 64 00 20 00 01 00 00 00 - 60 ea 00 00 01 00 00 00 d. .....`ê......

00000020 60 ea 00 00 `ê..

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Config
Nome da classe: <SEM CLASSE>
Hora da última escrita: 22-01-2009 - 10:29
Valor 0
Nome: LastClockRate
Tipo: REG_DWORD
Dados: 0x2625a

Valor 1
Nome: MinClockRate
Tipo: REG_DWORD
Dados: 0x260d4

Valor 2
Nome: MaxClockRate
Tipo: REG_DWORD
Dados: 0x263e0

Valor 3
Nome: FrequencyCorrectRate
Tipo: REG_DWORD
Dados: 0x4

Valor 4
Nome: PollAdjustFactor
Tipo: REG_DWORD
Dados: 0x5

Valor 5
Nome: LargePhaseOffset
Tipo: REG_DWORD
Dados: 0x138800

Valor 6
Nome: SpikeWatchPeriod
Tipo: REG_DWORD
Dados: 0x5a

Valor 7
Nome: HoldPeriod
Tipo: REG_DWORD
Dados: 0x5

Valor 8
Nome: MaxPollInterval
Tipo: REG_DWORD
Dados: 0xf

Valor 9
Nome: LocalClockDispersion
Tipo: REG_DWORD
Dados: 0xa

Valor 10
Nome: EventLogFlags
Tipo: REG_DWORD
Dados: 0x2

Valor 11
Nome: PhaseCorrectRate
Tipo: REG_DWORD
Dados: 0x1

Valor 12
Nome: MinPollInterval
Tipo: REG_DWORD
Dados: 0xa

Valor 13
Nome: UpdateInterval
Tipo: REG_DWORD
Dados: 0x7530

Valor 14
Nome: MaxNegPhaseCorrection
Tipo: REG_DWORD
Dados: 0xffffffff

Valor 15
Nome: MaxPosPhaseCorrection
Tipo: REG_DWORD
Dados: 0xffffffff

Valor 16
Nome: AnnounceFlags
Tipo: REG_DWORD
Dados: 0x5

Valor 17
Nome: MaxAllowedPhaseOffset
Tipo: REG_DWORD
Dados: 0x12c

Valor 18
Nome: FileLogSize
Tipo: REG_DWORD
Dados: 0x10000000

Valor 19
Nome: FileLogName
Tipo: REG_SZ
Dados: c:\windows\temp\w32time.log

Valor 20
Nome: FileLogEntries
Tipo: REG_SZ
Dados: 0-220

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Parameters
Nome da classe: <SEM CLASSE>
Hora da última escrita: 22-01-2009 - 9:50
Valor 0
Nome: ServiceMain
Tipo: REG_SZ
Dados: SvchostEntry_W32Time

Valor 1
Nome: ServiceDll
Tipo: REG_EXPAND_SZ
Dados: C:\WINDOWS\system32\w32time.dll

Valor 2
Nome: Type
Tipo: REG_SZ
Dados: Nt5DS

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Security
Nome da classe: <SEM CLASSE>
Hora da última escrita: 02-10-2008 - 7:40
Valor 0
Nome: Security
Tipo: REG_BINARY
Dados:
00000000 01 00 14 80 a8 00 00 00 - b4 00 00 00 14 00 00 00 ....¨...´.......

00000010 30 00 00 00 02 00 1c 00 - 01 00 00 00 02 80 14 00 0...............

00000020 ff 01 0f 00 01 01 00 00 - 00 00 00 01 00 00 00 00 ÿ...............

00000030 02 00 78 00 05 00 00 00 - 00 00 14 00 8d 00 02 00 ..x.............

00000040 01 01 00 00 00 00 00 05 - 0b 00 00 00 00 00 18 00 ................

00000050 ff 01 0f 00 01 02 00 00 - 00 00 00 05 20 00 00 00 ÿ........... ...

00000060 20 02 00 00 00 00 18 00 - 8d 00 02 00 01 02 00 00 ...............

00000070 00 00 00 05 20 00 00 00 - 23 02 00 00 00 00 14 00 .... ...#.......

00000080 9d 00 00 00 01 01 00 00 - 00 00 00 05 04 00 00 00 ................

00000090 00 00 18 00 9d 00 00 00 - 01 02 00 00 00 00 00 05 ................

000000a0 20 00 00 00 21 02 00 00 - 01 01 00 00 00 00 00 05 ...!...........

000000b0 12 00 00 00 01 01 00 00 - 00 00 00 05 12 00 00 00 ................

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\TimeProviders
Nome da classe: <SEM CLASSE>
Hora da última escrita: 02-10-2008 - 7:40

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\TimeProviders\NtpClient
Nome da classe: <SEM CLASSE>
Hora da última escrita: 02-10-2008 - 7:40
Valor 0
Nome: Enabled
Tipo: REG_DWORD
Dados: 0x1

Valor 1
Nome: InputProvider
Tipo: REG_DWORD
Dados: 0x1

Valor 2
Nome: AllowNonstandardModeCombinations
Tipo: REG_DWORD
Dados: 0x1

Valor 3
Nome: CrossSiteSyncFlags
Tipo: REG_DWORD
Dados: 0x2

Valor 4
Nome: ResolvePeerBackoffMinutes
Tipo: REG_DWORD
Dados: 0xf

Valor 5
Nome: ResolvePeerBackoffMaxTimes
Tipo: REG_DWORD
Dados: 0x7

Valor 6
Nome: CompatibilityFlags
Tipo: REG_DWORD
Dados: 0x80000000

Valor 7
Nome: EventLogFlags
Tipo: REG_DWORD
Dados: 0x0

Valor 8
Nome: DllName
Tipo: REG_SZ
Dados: C:\WINDOWS\system32\w32time.dll

Valor 9
Nome: SpecialPollTimeRemaining
Tipo: REG_MULTI_SZ
Dados:

Valor 10
Nome: SpecialPollInterval
Tipo: REG_DWORD
Dados: 0xe10

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\TimeProviders\NtpServer
Nome da classe: <SEM CLASSE>
Hora da última escrita: 02-10-2008 - 7:40
Valor 0
Nome: Enabled
Tipo: REG_DWORD
Dados: 0x1

Valor 1
Nome: InputProvider
Tipo: REG_DWORD
Dados: 0x0

Valor 2
Nome: AllowNonstandardModeCombinations
Tipo: REG_DWORD
Dados: 0x1

Valor 3
Nome: DllName
Tipo: REG_SZ
Dados: C:\WINDOWS\system32\w32time.dll

Nome da chave: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
W32Time\Enum
Nome da classe: <SEM CLASSE>
Hora da última escrita: 22-01-2009 - 9:42
Valor 0
Nome: 0
Tipo: REG_SZ
Dados: Root\LEGACY_W32TIME\0000

Valor 1
Nome: Count
Tipo: REG_DWORD
Dados: 0x1

Valor 2
Nome: NextInstance
Tipo: REG_DWORD
Dados: 0x1

[drtduarte via WinServerKB.com]

Well finally I found about this tool, it salved my life...
http://www.meinberg.de/english/sw/ntp.htm

Time is now synchronized on my network ;)

Take care,
David

--
Message posted via http://www.winserverkb.com

[Meinolf Weber [MVP-DS]]

Hello drtduarte,

Is the server registry from the PDCEmulator? On the PDCEmulator this should
be "NTP" not "Nt5DS".

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

Valor 2

Nome: Type
Tipo: REG_SZ
Dados: Nt5DS

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

[drtduarte via WinServerKB.com]

Hello Meinolf,

Thanks for your help.
Actually the registry is from one pc with xp not the server.
When you mean the PDCEmulator, you mean the server right?

The w32time setting on the server (win 2003 server small business) has NTP.

Regards,
David

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-server-ad/200901/1

[JPolicelli [MVP-DS]]

David,

It sounds as though you used a third party solution, which is fine. However,
you should also know that Windows has its own time service. Also, the
Windows Time Service is tightly integrated with Active Directory. You can
read more about it here:
http://technet.microsoft.com/en-us/library/cc773013.aspx.

--

JPolicelli, MVP - Directory Services

http://www.policelli.com
http://policelli.com/blog

This posting is provided AS IS with no warranties and confers no rights.
Always plan and test.

----

"drtduarte via WinServerKB.com" <u49032@uwe> wrote in message
news:909a899149518@uwe...

[Ace Fekay [Microsoft Certified Trainer]]

In news:90c191327db0e@uwe,
drtduarte via WinServerKB.com <u49032@uwe> requesting assistance, typed the
following:

> Hello Meinolf,
>
> Thanks for your help.
> Actually the registry is from one pc with xp not the server.
> When you mean the PDCEmulator, you mean the server right?
>
> The w32time setting on the server (win 2003 server small business)
> has NTP.
>
> Regards,
> David

As Meinolf mentioned, the Time service under Windows is intergrated with AD
and windows services. By Default, the domain controller that holds the PDC
Emulator Role is the time service for the domain. Also by default, ALL
machine in the domain will seek the domain controller holding the PDC
Emulator Role.

To configure the Time Service domain controller holding the PDC Emulator
Role, follow these steps to be only performed domain controller holding the
PDC Emulator Role:

net stop w32time
net time /setsntp:192.5.41.41
net start w32time

THis will set the time service to sync time with 192.5.41.41, a well known
US Naval time server on the internet. If you need a time service elsewhere,
here is a list:

A list of the Simple Network Time Protocol (SNTP) time servers that are
available on the Internet (US and International):
http://support.microsoft.com/kb/262680

There are no other registry changes, modifications, additions required, nor
any third party applications that need to be installed. It all works by
default, and it works nicely I may add.

--
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
ace...@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

[JPolicelli [MVP-DS]]

When WS03 was first released, I saw some odd behavior when using net time to
configure the Windows Time service. After working with PSS, I found out that
there were issues with using net time (known to PSS) and the supported
method for WS03 and later was w32tm.exe. To this day, and years later, I
have yet to see anything documented from MS stating that the net time should
not be used.

Nonetheless, I recommend that you do not use net time, but instead use the
w32tm.exe command. More specifically, see the following KB:
http://technet.microsoft.com/en-us/library/cc786897.aspx

--

JPolicelli, MVP - Directory Services

http://www.policelli.com
http://policelli.com/blog

This posting is provided AS IS with no warranties and confers no rights.
Always plan and test.

----

"Ace Fekay [Microsoft Certified Trainer]" <firstnam...@hotmail.com>
wrote in message news:ucmtTwCg...@TK2MSFTNGP05.phx.gbl...

[Meinolf Weber [MVP-DS]]

Hello drtduarte via WinServerKB.com,

Yes, the PDCEmulator is your SBS, no other DC can have the FSMO roles when
SBS is used. The PDCemulator in a domain is always the time source and all
other DC's sync with that one automatically. Member servers and workstations
will use one available DC for time sync. This ensures that all machines in
a domain have the same time. If there are time sync problems make sure that
a firewall is not blocking NTP port 123 UDP.

So you should not configure the XP to use another time source then the SBS.
If they have a time difference over 5 minutes you will got domain internal
problems.

Personal i would configure the SBS to an external time source and reconfigure
the clients to use the SBS as domain time server.

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

[Ace Fekay [Microsoft Certified Trainer]]

In news:49BEA856-8658-4E17...@microsoft.com,
JPolicelli [MVP-DS] <JPolice...@discussions.microsoft.com> requesting
assistance, typed the following:

> When WS03 was first released, I saw some odd behavior when using net
> time to configure the Windows Time service. After working with PSS, I
> found out that there were issues with using net time (known to PSS)
> and the supported method for WS03 and later was w32tm.exe. To this
> day, and years later, I have yet to see anything documented from MS
> stating that the net time should not be used.
>
> Nonetheless, I recommend that you do not use net time, but instead
> use the w32tm.exe command. More specifically, see the following KB:
> http://technet.microsoft.com/en-us/library/cc786897.aspx

Hi J,

I didn't realize that. I haven't had any trouble in the past with using the
net time command. So based on the article, we can simply state the following
without going through the procedure I outlined?

w32tm /config /manualpeerlist:192.5.41.41 /syncfromflags:manual
/reliable:yes /update

Thanks,

Ace

[drtduarte via WinServerKB.com]

Thank you all for the great help.

I was using net time commands, maybe that was the reason for having issues...
I will try your suggestions as soon as possible, right now all the network is
using the ntp server refered above, the clients get the time from the server,
and the server from an external source.

Regards,
David

[JPolicelli [MVP-DS]]

You example below is correct.

--

JPolicelli, MVP - Directory Services

http://www.policelli.com
http://policelli.com/blog

This posting is provided AS IS with no warranties and confers no rights.
Always plan and test.

----

"Ace Fekay [Microsoft Certified Trainer]" <firstnam...@hotmail.com>

wrote in message news:Ot#hkPKgJ...@TK2MSFTNGP02.phx.gbl...

[Ace Fekay [Microsoft Certified Trainer]]

In news:4E9E9DBD-9A9D-42BB...@microsoft.com,
JPolicelli [MVP-DS] <JPolice...@discussions.microsoft.com>, posted the
following:

> You example below is correct.

Thanks!