Net time errors out or slow producing result, w2k3 domain
Posted on 2009-04-06
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