• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 448
  • Last Modified:

Wrong Time Synchronization in the Domain

We have 2 DCs  and both have same wrong time. how can I fix it?

sys info:
server2003
0
osho929
Asked:
osho929
1 Solution
 
Vishnu KiranCommented:
Hi,

Please go through the below Microsoft KB article  on how to configure an authoritative time server in Windows Server 2003:

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

Regards,
Vishnu.
0
 
dolomitiCommented:
hi,
see NET TIME Help
verify NET TIME /QUERYSNTP

then try to set

NET TIME /SETSNTP:time.windows.com

NTP uses poer 123 UDP.

bye
vic
0
 
osho929Author Commented:
dolomiti:
should I run these two commands in Both DCs &  is it safe to run it.
verify NET TIME /QUERYSNTP
NET TIME /SETSNTP:time.windows.com
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
oBdACommented:
The 816042 article is plain overkill in most cases. It explains how to turn *any* W2k3 server into an authoritative time server, but in an AD domain, DCs are authoritative time servers *by* *default*.
Usually, the *only* machine in an AD domain that needs to be configured to sync with an outside time source is the PDC emulator. Other DCs will sync with the PDCe, and members will sync with the DC authenticating them.
"net time /querysntp" or "net time /setsntp" will *ONLY* do something useful on the PDCe; a manually configured time server will by default be ignored by domain members, they'll use the domain hierarchy instead. In general, "net time" is deprecated (it dates back to NT) and shouldn't be used anymore, use the new tool w32tm.exe instead.
In other words: on the PDCe, open a command prompt and enter (replacing <1.2.3.4> with the time server of your choice; the ,0x8 at the end will tell the time service to run in ntp client mode):

w32tm /config /manualpeerlist:<1.2.3.4>,0x8 /update
w32tm /resync

Time servers are here (I wouldn't use the default "time.windows.com"; I've found it to be unreliable); pick a time server geographically close to you, for example one of these:

A list of the Simple Network Time Protocol (SNTP) time servers that are available on the Internet
http://support.microsoft.com/kb/262680

The pool.ntp.org project
http://www.pool.ntp.org/

If your PDCe is more than 5 minutes off the real time, run this after production hours to prevent possible authentication problems before the time service on the clients gets a chance to adjust its time according to the new PDC time.
0
 
osho929Author Commented:
if I used The pool.ntp.org project ,is this right

w32tm /config /manualpeerlist:< .sg.pool.ntp.org,0.asia.pool.ntp.org,2.asia.pool.ntp.org                             >,0x8 /update

w32tm /resync

Than all client should restart their machine.
0
 
oBdACommented:
Not quite, the "<...>" was just to indicate the server, it's not part of the syntax; and for several servers, the list has to be space separated:

w32tm /config /manualpeerlist:"sg.pool.ntp.org,0x8 0.asia.pool.ntp.org,0x8 2.asia.pool.ntp.org,0x8" /update
w32tm /resync

If this doesn't work try it with a single server first:
w32tm /config /manualpeerlist:sg.pool.ntp.org,0x8 /update

You only need to run this on the PDCe; there should be no need to do anything on the clients, in all likelihood, they should have the same time as the DCs already, and follow up on the time changes of the DCs as soon as they sync the next time.
You can force a resync remotely by using
w32tm /resync /computer:<Computer>
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now