Re: Date changed to January 1, 2000 on January 1, 2007 on servers

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

XP_2600,

refer to the following MS article for an in-depth explanation of the Windows 2003 time services: http://technet2.microsoft.com/WindowsServer/en/library/71e76587-28f4-4272-a3d7-7f44ca50c0181033.mspx?mfr=true

In short, make sure the PDC emulator from the root domain is always having the correct time, by synchronizing it with an external time source (Internet, atom clock receiver). By default, each Windows 2000/XP/2003 client will automatically synchronize its time with the forest as soon as it is joined to the domain. This is done using the SNTP protocol, which is a bit more intelligent then the standard NTP protocol.

To restore the default behaviour of time synchronization with the domain hierarchy, follow the procedure listed in the following article:
http://technet2.microsoft.com/WindowsServer/f/?en/library/8990703a-a197-4717-b6e5-b7406d9f91f01033.mspx
These commands must be run on every client (workstation/member server) which has been configured differently.

--
Kind regards,

Erik Cheizoo
eXcellence & Difference
We keep your business running
----------------------------------------------
Always test in a non-production environment!
----------------------------------------------

"XP_2600" <XP2600@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3E03010E-96A8-49D8-9946-8E574A2CCBD1@xxxxxxxxxxxxxxxx

Well i have a question always bothering me, when i build a domain using
windows 2003 what is the best scenario ? am i should make all clients using
the domain controller as a time server ? and if so am i need to configure
anything in the domain controller to allow it ? or i should keep the default
settings and dont bother myself with it ? and about the clients i should
configure them using Group Policy, and whats the options should or may i need
to set in the time server and from where i should configure it ? net time ?
and enable the time server service in services or there is a command line or
interface to enable the time server ?, thanks so much and sorry for bothering
you.
"Joe Richards [MVP]" wrote:

So I guess you are getting messages saying the DCs can't replicate
because it has been too long since the last replication?

If so, in this very special case you may want to look at the steps that
are described in

http://support.microsoft.com/kb/317097

I would go chase down the people who are managing the NTP server you are
using and ask them WTF happened because that is why you had a problem.
That didn't come out of Windows, that is whatever your external time
source is. The problem probably crept up around midnight UTC at a guess
when the NTP servers ran into some sort of issue. I have seen crap like
that happen before. Every time it was related to someone not keeping
firmware levels or IOS levels up to date by several years.

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


Sade wrote:
> On January 1 2007, all 6 domain controllers started having errors when > the
> dates on the server changed to January 1 2000 around 6.30pm. After > about one
> hour the time corrected itself to the correct date and time but > replication
> has stopped since then because of that problem, how do I fix this.


.

Quantcast