Net time errors out or slow producing result, w2k3 domain

I recently promoted a new server to become the PDC/authoritive time server.  When I run a 'net time /querysntp' I get the new server's name as SNTP value.  When I do a net time command it always produces the time from the old PDC which is fine, but recently we shut off the old PDC (not yet demoted) and when we run a net time command it will either pop error 51 or take an extremely long time to return the time from the new PDC.  

Is this normal that the clients will stick to the old dc for things like time queries?  Is there a command i can put in my logon scripts after i do the demotion that will force maybe a resync with the new pdc?  I'm getting a bit nervous that things are still sticking to that old PDC and i'll have problems when i turn it off
jmtomanAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
zelron22Connect With a Mentor Commented:
It is normal if you haven't demoted it and cleaned out DNS.  NET TIME is an old command from NT 4 and no longer needed.  Domain member machines in 200x get their time from any available DC, and the DCs get it from the PDC emulator.

Because you haven't demoted it, DNS still has service records and DC records for the old DC, this is why they're still trying to get to it.
0
 
Justin OwensITIL Problem ManagerCommented:
Was the old DC still running the time service at the time of power off?
0
 
Justin OwensConnect With a Mentor ITIL Problem ManagerCommented:
zelron22 went where I was headed.  Once you demote your old DC and DNS is cleaned up, you should be fine.
0
 
PopeyediceclayCommented:
You might also try this command on the client:
w32tm -s

Here the KB from MS:
http://support.microsoft.com/kb/216734
0
All Courses

From novice to tech pro — start learning today.