Event ID 11 from the w32time source, win2k server

[Joel]

Hi,

A while back I posted a question about this very subject. At the time I did
not believe that having the correct time on my win2k server was particularly
important. I was more concerned that workstations in the domain have the
same time as the domain controllers.

Well, things have changed in the meanwhile, and I now want the servers in
the domain to have the correct time. I discovered that the servers have a
pretty bad time keeping the correct time and this made things difficult on a
number of fronts. And I still want the win 2k pro workstations time to be
synced up to the servers.

So, on the domain controller with the PDC emulator role I ran from a command
prompt:
NET TIME \\nameofDC /SETSNTP:"18.145.0.30 140.239.15.7 158.121.95.4
192.5.41.40" /SET
(the ip addresses are standard time sources on the web).
On the second domain controller and on all the workstations I ran:
NET TIME \\NAMEOFCLIENT /SETSNTP:nameofDC /SET

I believe that this is working now and that the server is now keeping the
correct time. But why do I still recieve the event id 11 warning from the
w32time source which reads "The NTP server didn't respond" in the system
log? Is this normal, and do I just live with it, or is there some other
configuration I ought to put in place?

Also, I'd like to know exactly how this command is supposed to work. Does
my server use the first ip in the list and if unable to contact it, does it
then go to the next time source in the list?

Thank you for any insight. /Joel

 

[David Pharr [MSFT]]

All your client computers should get their time from their authenticating
domain controllers, the domain controllers should use an algorithm to
determine their order of precedence within the chain and the PDC Emulator
at the root of the forest should be authoritative for the entire forest.
This will only happen if all your clients have the W32Time service set to
Automatic and Started, and their W32Time Type registry value set to Nt5DS
at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters.


223184 Registry Entries for the W32Time Service
http://support.microsoft.com/?id=223184

The PDC Emulator should be the only machine that is different - you can
configure this machine to select a time server on the Internet according to
the following kb article:

216734 How to Configure an Authoritative Time Server in Windows 2000
http://support.microsoft.com/?id=216734

The event 11 errors are occurring because the NTP Server is not responding
for some reason - if you're behind a firewall the appropriate ports could
be blocked. When the connection is made to the NTP server the destination
port is normally UDP port 123 but the source port can be a random UDP port
above 1023. You will have to make sure that UDP ports above 1023 are open
for the NTP Server's response. You can run w32tm -v -once to gather
information about the cause of the failure.

As far as the time server list, you can use mutliple time servers separated
by commas or spaces - try using spaces between the ip addresses.

For information on how all this works, review the Windows Time White Paper
at http://www.microsoft.com/windows2000/docs/wintimeserv.doc

David Pharr, (e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Joel" <jwolfe(removethis)@digimarc.com>
| Subject: Event ID 11 from the w32time source, win2k server
| Date: Fri, 7 May 2004 14:38:54 -0400
| Lines: 34
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.win2000.active_directory
| NNTP-Posting-Host: 198.70.207.26
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.win2000.active_directory:78896
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| Hi,
|
| A while back I posted a question about this very subject. At the time I
did
| not believe that having the correct time on my win2k server was
particularly
| important. I was more concerned that workstations in the domain have the
| same time as the domain controllers.
|
| Well, things have changed in the meanwhile, and I now want the servers in
| the domain to have the correct time. I discovered that the servers have a
| pretty bad time keeping the correct time and this made things difficult
on a
| number of fronts. And I still want the win 2k pro workstations time to be
| synced up to the servers.
|
| So, on the domain controller with the PDC emulator role I ran from a
command
| prompt:
| NET TIME \\nameofDC /SETSNTP:"18.145.0.30 140.239.15.7 158.121.95.4
| 192.5.41.40" /SET
| (the ip addresses are standard time sources on the web).
| On the second domain controller and on all the workstations I ran:
| NET TIME \\NAMEOFCLIENT /SETSNTP:nameofDC /SET
|
| I believe that this is working now and that the server is now keeping the
| correct time. But why do I still recieve the event id 11 warning from the
| w32time source which reads "The NTP server didn't respond" in the system
| log? Is this normal, and do I just live with it, or is there some other
| configuration I ought to put in place?
|
| Also, I'd like to know exactly how this command is supposed to work. Does
| my server use the first ip in the list and if unable to contact it, does
it
| then go to the next time source in the list?
|
| Thank you for any insight. /Joel
|
|
|

 

[Joel]

Wow! Thanks David--that's all good information and it's much clearer now.

I'm thinking that the event 11 errors are because of firewall/network
issues, but that it actually is getting through most of the time. I get a
few of them now every day, but I'm tending to ignore them now that the
server is actually keeping pretty good time. Here are the results of the
w32tm -v -once command--I don't believe that it indicates a problem at this
particular moment in time:

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 156250 , Incr 156250 fAdjust 0
W32Time: END:Line 2503
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1407
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 156250
W32Time: CurrentTime = 9766
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 807
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2596
W32Time: BEGIN:InitTmData
W32Time: END:Line 2618
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - 18.145.0.30 140.239.15.7 158.121.95.4 192.5.41.40
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 156250 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1295
W32Time: END:Line 864
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr 0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 1 NIC.
W32Time: bind failed: 0x80072740
W32Time: Logging event 0xC0000031. 15 min until this event is allowed again.
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1407
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

All your client computers should get their time from their authenticating
domain controllers, the domain controllers should use an algorithm to
determine their order of precedence within the chain and the PDC Emulator
at the root of the forest should be authoritative for the entire forest.
This will only happen if all your clients have the W32Time service set to
Automatic and Started, and their W32Time Type registry value set to Nt5DS
at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters.


223184 Registry Entries for the W32Time Service
http://support.microsoft.com/?id=223184

The PDC Emulator should be the only machine that is different - you can
configure this machine to select a time server on the Internet according to
the following kb article:

216734 How to Configure an Authoritative Time Server in Windows 2000
http://support.microsoft.com/?id=216734

The event 11 errors are occurring because the NTP Server is not responding
for some reason - if you're behind a firewall the appropriate ports could
be blocked. When the connection is made to the NTP server the destination
port is normally UDP port 123 but the source port can be a random UDP port
above 1023. You will have to make sure that UDP ports above 1023 are open
for the NTP Server's response. You can run w32tm -v -once to gather
information about the cause of the failure.

As far as the time server list, you can use mutliple time servers separated
by commas or spaces - try using spaces between the ip addresses.

For information on how all this works, review the Windows Time White Paper
at http://www.microsoft.com/windows2000/docs/wintimeserv.doc

David Pharr, (e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Joel" <jwolfe(removethis)@digimarc.com>
| Subject: Event ID 11 from the w32time source, win2k server
| Date: Fri, 7 May 2004 14:38:54 -0400
| Lines: 34
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.win2000.active_directory
| NNTP-Posting-Host: 198.70.207.26
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.win2000.active_directory:78896
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| Hi,
|
| A while back I posted a question about this very subject. At the time I
did
| not believe that having the correct time on my win2k server was
particularly
| important. I was more concerned that workstations in the domain have the
| same time as the domain controllers.
|
| Well, things have changed in the meanwhile, and I now want the servers in
| the domain to have the correct time. I discovered that the servers have a
| pretty bad time keeping the correct time and this made things difficult
on a
| number of fronts. And I still want the win 2k pro workstations time to be
| synced up to the servers.
|
| So, on the domain controller with the PDC emulator role I ran from a
command
| prompt:
| NET TIME \\nameofDC /SETSNTP:"18.145.0.30 140.239.15.7 158.121.95.4
| 192.5.41.40" /SET
| (the ip addresses are standard time sources on the web).
| On the second domain controller and on all the workstations I ran:
| NET TIME \\NAMEOFCLIENT /SETSNTP:nameofDC /SET
|
| I believe that this is working now and that the server is now keeping the
| correct time. But why do I still recieve the event id 11 warning from the
| w32time source which reads "The NTP server didn't respond" in the system
| log? Is this normal, and do I just live with it, or is there some other
| configuration I ought to put in place?
|
| Also, I'd like to know exactly how this command is supposed to work. Does
| my server use the first ip in the list and if unable to contact it, does
it
| then go to the next time source in the list?
|
| Thank you for any insight. /Joel
|
|
|