time, new dc

  • Thread starter Thread starter kb
  • Start date Start date
K

kb

I brought an additional, new dc up into our ads single
domain forest yesterday. Today, I transferred the pdc and
rid fsmo roles to the new dc.
I started receiving these errors on the new dc:
Event Source: w32time
Event Category: None
Event ID: 54
The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible.

So I ran the net time /setsntp:xxxxx command on the new dc
and rebooted it and the other dc's.
I followed Q312534 and ran the resycnch commands, but
received an error? shown here:

C:\>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.


C:\>w32tm -s
RPC to local server returned 0x6b5

C:\>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.

The dc's are all still pointing to the OLD pdc role holder
for time. Do I need to do something else? Do I have a
problem?
TIA,
Karen
 
Back
Top