On the old 2003 DC, check HKLM\System\CurrentControlSet\Services\W32Time\Parameters\Type. It should be "NT5D5". If it shows "NTP", then the DC is synchronizing time with an external time source. It was probably the forest root PDCe in the past, but if it no longer is then on that DC run Net stop w32time W32tm /unregister W32tm /register Net start w32time
That will clear out the old time configuration and reset it to a domain hierarchy configuration. From: [email protected] [mailto:[email protected]] Sent: Monday, January 7, 2013 8:22 AM To: NT System Admin Issues Subject: RE: DC server 2003 Time service >From my PC: (Looks like I have everything working except the first one. It is an old 2003 DC.) Why is it being so difficult? All the other 2008 DC's and 2003 DC's are behaving except it? Where can I look? C:\windows\system32>w32tm /monitor 030405MF663P44.IMCU.local[10.0.10.5:123]: ICMP: 6ms delay NTP: +0.0225576s offset from 081012210GL255.IMCU.local RefID: tick.usno.navy.mil [192.5.41.40] Stratum: 2 0304090304zu55.IMCU.local[10.0.50.205:123]: ICMP: 0ms delay NTP: +0.0127904s offset from 081012210GL255.IMCU.local RefID: 081012210GL255.IMCU.local [10.0.50.2] Stratum: 4 0302040304zu77.IMCU.local[10.0.90.205:123]: ICMP: 13ms delay NTP: +0.0002909s offset from 081012210GL255.IMCU.local RefID: 081012210GL255.IMCU.local [10.0.50.2] Stratum: 4 0810123404XB44.IMCU.local[10.0.10.2:123]: ICMP: 9ms delay NTP: +0.0136959s offset from 081012210GL255.IMCU.local RefID: 081012210GL255.IMCU.local [10.0.50.2] Stratum: 4 081012210GL255.IMCU.local *** PDC ***[10.0.50.2:123]: ICMP: 0ms delay NTP: +0.0000000s offset from 081012210GL255.IMCU.local RefID: white.web-ster.com [65.182.224.39] Stratum: 3 08101223061O77.IMCU.local[10.0.90.2:123]: ICMP: 10ms delay NTP: +0.0069312s offset from 081012210GL255.IMCU.local RefID: 081012210GL255.IMCU.local [10.0.50.2] Stratum: 4 From: Ken Schaefer [mailto:[email protected]] Posted At: Friday, January 4, 2013 12:05 AM Posted To: [email protected]<mailto:[email protected]> Conversation: DC server 2003 Time service Subject: RE: DC server 2003 Time service You need to read this: http://technet.microsoft.com/en-us/library/cc773013(v=ws.10).aspx Cheers Ken From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Friday, 4 January 2013 3:33 AM To: NT System Admin Issues Subject: DC server 2003 Time service I am bringing 2008 R2 servers on line to take the FSMO jobs. I have set one of them as a W32time server but my pc's are still getting time from the old 2003 DC SNTP server??? Any ideas on how to correct this? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
