Link to home
Start Free TrialLog in
Avatar of cobmo
cobmoFlag for United States of America

asked on

Configure Windows Time on PDC Windows 2008 R2 Server

OK something is out of whack here.  i noticed my Exchange server drifted and was causing problems.  My PDC is supposed to be pointing to an external source pool.ntp.org.  It was working fine initially.  I can ping pool.ntp.org.

My mail server is pointing to a local DC but my PDC is pointing to another DC in another building.  On the PDC, I have run the following commands:

net stop w32time
w32tm -unregister
w32tm -register
net start w32time
w32tm /config /manualpeerlist:pool.ntp.org,0x8 /syncfromflags:MANUAL /reliable:yes /update
w32tm /resync /rediscover

When all is done I type Net Time and it still shows the DC in the other building.  How can I flush the time sync and start over?  What am I doing wrong?  I know this is all I did originally and the mail server would have pointed to the PDC not the other DC.
Time is all out of synce because everything is pointing to everything else but what it is supposed to be looking at.
Avatar of Chris
Chris
Flag of United Kingdom of Great Britain and Northern Ireland image

As a general rule all computers in a forest will pull their time from the PDC Emulator for the first domain in the forest. As the server in question is apparently pulling it's time from another DC are you sure that it's not I'm fact that DC that holds the PDC Emulator role?
Avatar of cobmo

ASKER

Yes netdom query fsmo displays the 5 roles as the PDC named Ball11.  When I run the net time command on it it shows Ball09 as the time server.  Not sure why it wont take over after running the command.  Maybe all I can do is reboot it?
ASKER CERTIFIED SOLUTION
Avatar of cobmo
cobmo
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of cobmo

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for cobmo's comment #a38364052

for the following reason:

Figured it out unassisted.
Not objecting to this being closed but as you've worked out the solution you should mark your answer as a solution rather than just deleting.
Avatar of cobmo

ASKER

Sorry it was not my intenet to delete.  I thought I posted my solution and accepted it as the solution here.
Avatar of cobmo

ASKER

PDC was not the acting time server bc it pointed to another DC in the domain.  Reset time service while DC was stopped and it came back up.  Not sure what caused the failure but resolved without reboot.