it is, but now I'm questioning if the commas should be removed 

  

Jean-Paul Natola

 


From: [email protected]
To: [email protected]
Subject: RE: [NTSysADM] time not syncing
Date: Mon, 17 Feb 2014 17:18:40 +0000









Is the PDC virtual?  If it is, it could be pulling the time from the vm host.  
Is the vmhost set to the proper NTP server 
(”0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org”)
  and not the PDC?
 
 
 


From: [email protected] [mailto:[email protected]]
On Behalf Of J- P

Sent: Monday, February 17, 2014 7:50 AM

To: [email protected]

Subject: [NTSysADM] time not syncing


 

Hi all,



i have follows these instructions to the letter, and have confirmed the values 
exist and are accurate in the registry of the 2008r2 DC, it remains 10 minutes 
off



All the computers, clients and servers, have the same time so its not causing 
any authentication issues (thankfully) but its annoying not be able to get the 
correct time


First, locate your PDC Server. Open the command prompt and type:
C:\>netdom /query fsmo
Log in to your PDC Server and open the command prompt.
Stop the W32Time service: C:\>net stop w32time
Configure the external time sources, type:
C:\> w32tm /config /syncfromflags:manual 
/manualpeerlist:”0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org”
Make your PDC a reliable time source for the clients. Type: C:\>w32tm /config 
/reliable:yes
Start the w32time service: C:\>net start w32time
The windows time service should begin synchronizing the time. You can check the 
external NTP servers in the time configuration by typing:
C:\>w32tm /query /configuration


when i run this command w32tm /stripchart /computer:0.pool.ntp.org /samples:5 
/dataonly



C:\>w32tm /stripchart /computer:0.pool.ntp.org /samples:5 /dataonly

Tracking 0.pool.ntp.org [15.126.193.186:123].

Collecting 5 samples.

The current time is 2/17/2014 10:55:41 AM.

10:55:41, -607.5560514s

10:55:43, -607.5602488s

10:55:45, -607.5647196s

10:55:47, -607.5687176s

10:55:49, -607.5880149s

                                          

Reply via email to