Solved

Net time errors out or slow producing result, w2k3 domain

Posted on 2009-04-06
4
1,186 Views
Last Modified: 2012-05-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
0
Comment
Question by:jmtoman
  • 2
4 Comments
 
LVL 15

Accepted Solution

by:
zelron22 earned 300 total points
ID: 24079896
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
 
LVL 31

Expert Comment

by:Justin Owens
ID: 24079899
Was the old DC still running the time service at the time of power off?
0
 
LVL 31

Assisted Solution

by:Justin Owens
Justin Owens earned 200 total points
ID: 24079916
zelron22 went where I was headed.  Once you demote your old DC and DNS is cleaned up, you should be fine.
0
 
LVL 3

Expert Comment

by:Popeyediceclay
ID: 24080026
You might also try this command on the client:
w32tm -s

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

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Instant VM Recovery 4 94
SolarWind and DNS Server 12 78
File Server Migration from 2003 to 2008R2 3 70
Questions about DHCP migration 5 61
by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
This tutorial gives a high-level tour of the interface of Marketo (a marketing automation tool to help businesses track and engage prospective customers and drive them to purchase). You will see the main areas including Marketing Activities, Design …
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question