W32time

  • Thread starter Thread starter Moreno
  • Start date Start date
M

Moreno

Hi everybody!

Can anyone tell me how can I correclty configure my
W32TIME service on my W2K Active Directory domain? (the
domain reflects the "SINGLE DOMAIN" and "MULTIPLE SITE"
configuration with 4 sites and 6 domain controllers).

The common errors in the event viewer are:

1) "The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible."
(event ID 54)

2) "Because of repeated network problems, the time service
has not been able to find a domain controller to
synchronize with for a long time. To reduce network
traffic, the time service will wait 960 minutes before
trying again. No synchronization will take place during
this interval, even if network connectivity is restored.
Accumulated time errors may cause certain network
operations to fail. To tell the time service that network
connectivity has been restored and that it should
resynchronize, execute "w32tm /s" from the command line."
(EVENT ID 64)

If possible, I would like to configure the Time Service to
refer to an INTERNAL SERVER CLOCK (e.g. one of the domain
controllers in the domain).

Thanks a lot!

Bye.

Moreno
(Italy)
 
| Hi everybody!
|
| Can anyone tell me how can I correclty configure my
| W32TIME service on my W2K Active Directory domain? (the
| domain reflects the "SINGLE DOMAIN" and "MULTIPLE SITE"
| configuration with 4 sites and 6 domain controllers).
|
| The common errors in the event viewer are:
|
| 1) "The Windows Time Service was not able to find a Domain
| Controller. A time and date update was not possible."
| (event ID 54)
|
| 2) "Because of repeated network problems, the time service
| has not been able to find a domain controller to
| synchronize with for a long time. To reduce network
| traffic, the time service will wait 960 minutes before
| trying again. No synchronization will take place during
| this interval, even if network connectivity is restored.
| Accumulated time errors may cause certain network
| operations to fail. To tell the time service that network
| connectivity has been restored and that it should
| resynchronize, execute "w32tm /s" from the command line."
| (EVENT ID 64)
|
| If possible, I would like to configure the Time Service to
| refer to an INTERNAL SERVER CLOCK (e.g. one of the domain
| controllers in the domain).
|
| Thanks a lot!
|
| Bye.
|
| Moreno
| (Italy)
|
|
|
|


Moreno,

You can set the preferred time server by open the command prompt and
issuing the following command:

net time /setsntp:<TIME SOURCE>

Replace <TIME SOURCE> with the NetBios name or IP address of the server you
want to be the time source.

You can also set this via Registry Editor by nagivating to:

HKLM\System\CCS\Services\W32Time\Parameters\NTP Server and setting the
NetBios name or IP address of the time source there



Chad A. Lacy
Windows 2000 Directory Services

==================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Moreno says...
Hi everybody!

Can anyone tell me how can I correclty configure my
W32TIME service on my W2K Active Directory domain? (the
domain reflects the "SINGLE DOMAIN" and "MULTIPLE SITE"
configuration with 4 sites and 6 domain controllers).

The common errors in the event viewer are:

1) "The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible."
(event ID 54)

2) "Because of repeated network problems, the time service
has not been able to find a domain controller to
synchronize with for a long time. To reduce network
traffic, the time service will wait 960 minutes before
trying again. No synchronization will take place during
this interval, even if network connectivity is restored.
Accumulated time errors may cause certain network
operations to fail. To tell the time service that network
connectivity has been restored and that it should
resynchronize, execute "w32tm /s" from the command line."
(EVENT ID 64)

If possible, I would like to configure the Time Service to
refer to an INTERNAL SERVER CLOCK (e.g. one of the domain
controllers in the domain).

Thanks a lot!

Bye.

Moreno
(Italy)
Click to expand...
Hello Moreno,

first make sure that you DNS and DCs are working well (test with netdiag and
dcdiag out of the support tools).

OK, talking about the timeservice, here's the default behavior:

Member Servers and Clients get the time from their DC.
DCs are getting their time from the DC which holds the PDC-Emulator in the
Domain.
the DCs holding the PDC-Emulator FSMO-Role get their time from upperlevel
Domains (PDC-Emlulators again).

Therefore it is essential that the PDC-Emulator of your domain (root domain if
you would have more than one) is getting the time of a good timesource. If it
does not get a valid time for a specific time it'll refuse the service to the
other machines.

You should set your PDC-Emulator to use NTP from a NTP-Source out of the
Internet or get a external clock for the PDC. You'd also be able to configure
it to trust his Bios-Clock, but I wouldn't recommend that in a production
environment.
To set the NTP-Source use the "net time /setsntp:"ip1 ip2 ip3"" command, keep
in mind to separate the IPs by spaces and put the thing in hyphens if you
specify more than one.

Just do this on the PDC-Emulator of your domain. All other servers should use
the default behavior, you can verify that by controlling the registry key
HKLM\System\CurrentControlSet\Services\w32time\Parameters
type = Nt5DS

Hope this helps.

Gruesse - Sincerely,

Ulf B. Simon-Weidner
 
Hi Ulf!

Thank you very much for your reply!
I'll try immediately!

Have a nice day!

Moreno
 
Moreno says...
Hi Ulf!

Thank you very much for your reply!
I'll try immediately!

Have a nice day!

Moreno
Click to expand...
Hello Moreno,

thanks and you're welcome.

Keep us uptodate if ti's working, if you have additional questions let us know.


Gruesse - Sincerely,

Ulf B. Simon-Weidner
 
Back
Top