Re: Time Service has Jumped to Another DC! Please help.

I want to add something else here. If I stop the net time service on the
remote domain controllers and do a 'net time' they point back to the master
DC like they should. If I enabled the net time service and perform a w32tm
/resync and then a net time, they are pointing at themselves again. Why do
they not stay pointing at the PRIMARY DC like they should?



"IT_Guru" <corey@xxxxxxxx> wrote in message
news:ex3xFrejHHA.5012@xxxxxxxxxxxxxxxxxxxxxxx
Okay this dosent make any sense.

I have the master DC configured to sync with an external time source,
however when ever a net time on any of my domain controllers, they are
syncing to a DIFFERENT domain controller then my master dc! If i stop the
net time service on the dc all other dc's are looking at, once a
replication occurs they will all be pointing to a different one that does
not have the time service stopped, but none of them want to point back to
the MASTER even though I have run the following command:

w32tm /config /syncfromflags:domhier /update

and restart the time service afterwards


Wtf is going on!



"IT_Guru" <corey@xxxxxxxx> wrote in message
news:%23$XXZAejHHA.1624@xxxxxxxxxxxxxxxxxxxxxxx
Hi Jorge,

Thanks for the quick reply. I am presuming the article you pointed me to
is relevant for member domain controllers as well? or in other words DC's
that do not hold the master roles? This problem just cropped up within
the last three days and I am trying to pin-point what may have caused
this bizare bahviour.

Also, all DC's are members of the same domain and properly seperated into
sites.

Thanks


"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:438C9D29-CC51-443B-9C17-F2D7DA66BB0F@xxxxxxxxxxxxxxxx
Hi
Each DC get the date from the PDCe for their domain, and all existing
PDCes should sync their Date with the PDCe at the Root Domain.
By default the non-DCs take it from the authenticated DC which get it
from the PDCe for that domain.
Make sure that the correct subnets are properly assigned so the clients
don't try to connect to the wrong DC.

How to configure an authoritative time server in Windows Server 2003
http://support.microsoft.com/kb/816042
To restore the default behaviour of time synchronization with the domain
hierarchy, follow the procedure listed in the following article:
http://technet2.microsoft.com/WindowsServer/f/?en/library/8990703a-a197-4717-b6e5-b7406d9f91f01033.mspx
--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"[c]" <no@xxxxxxxxx> wrote in message
news:OJtNStdjHHA.4248@xxxxxxxxxxxxxxxxxxxxxxx
In our domain of multiple sites - for some reason the internal time
server in our domain is a remote site's domain controller. I was always
under the impression that the first DC created in an AD environment and
that with which holds the PDC emulator role is by default the
authorative domain time server. Can someone explain why the time server
may have jumped to another DC in our environment, especailly one not
holding any master roles and is actually a remote site server?

Even the PDC (holding all master roles and the forst root server) shows
this remote server as its time server when running net time?

Now the other problem, on the PDC I have tried changing the time server
to point back to itself(windows 2003 domain) but it keeps displaying
the remote DC as its time server. I ran this command, w32tm /config
/manualpeerlist:time.microsoft.com /syncfromflags:manual /reliable:yes
/update. The command stated it completed successfully. i restarted the
net logon service, didnt make a difference so I restarted the whole box
and it still shows this remote site server as the time server.

Thanks.








.

Relevant Pages

  • Re: Time Issue
    ... Does your Samba still act as a time server? ... To verify that the time service is synchronizing time at the command prompt, ... net time /setsntp ...
    (microsoft.public.windows.server.networking)
  • time service
    ... i can't make the pdc a time server using the software i have because it is a cluster node and it disables the time service which could cause a problem since it is important that the time service runs for the cluster. ... Configure to sync from External time source using the net command, 'net time /setsntp:'. ...
    (microsoft.public.win2000.general)
  • time service
    ... i can't make the pdc a time server using the software i have because it is a cluster node and it disables the time service which could cause a problem since it is important that the time service runs for the cluster. ... Configure to sync from External time source using the net command, 'net time /setsntp:'. ...
    (microsoft.public.win2000.advanced_server)
  • time service
    ... i can't make the pdc a time server using the software i have because it is a cluster node and it disables the time service which could cause a problem since it is important that the time service runs for the cluster. ... Configure to sync from External time source using the net command, 'net time /setsntp:'. ...
    (microsoft.public.win2000.networking)
  • Re: Change Domain Time Server
    ... If I do a simple net time command, this should return the domain time server time, right? ... You are missing the time source on your registry. ... Your pdc should now return the correct time and you can now sync all other DCs to get time from the PDC. ...
    (microsoft.public.windows.server.general)