> I have a 2K server as the root of my forest. It is the
> only 2K system. All of my other servers are NT4 and so are
> my workstations.
> The server keeps logging the event id 62 & 64's. Basically
> it is trying to resynchronize with something and it is
> failing. I reviewed Q258059 from Microsoft. It was close
> but not quite what I was looking for. Do I need to have
> the server going out there to do a synch? Also if I do,
> how can I go about correcting the issue since this is the
> PDC and not just added to an NT4 network where an NT4
> server is the PDC?
> FYI: I think whenever it's trying to do a synch it is
> killing my network. What I mean by that is my network is
> going down at 4:45 almost every single day and magically
> comes back on at 10:00. Weird, but I think it is related
> to the time synch issue.
> Many thanks in advance.
Like Greg says, you should manually configure the DC to synchronise
net time /setsntp:time.nist.gov
( or your choice of server. )
As detailled in the following article:
How to Configure an Authoritative Time Server in Windows (Q216734)
If you do not wish to have the DC sync to an external source, then you can
edit the registry:
The value 'Type" ( REG_SZ ) can have one of 3 values:
Nt5DS Sync with domain heirarchy ( default );
NTP Sync with manually configured source;
NoSync Do not sync.
If you set it to NoSync, then it will not throw errors in the Eventlog.
2000\XP clients should be set to sync from the Domain, by *not* manually
configuring a NTP time source:
net time /querysntp will list any manually configured time source;
net time /setsntp: will clear any previously configured.
Please see the following article for a good discussion onW32Time:
The Windows Time Service