[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 413
  • Last Modified:

Point Servers to another NTP Server

Our client systems are picking up NTP via the DHCP server.  What is the best method to point static IP servers to the same source as the clients?
0
iNetSystem
Asked:
iNetSystem
1 Solution
 
Felix LevenSenior System and DatabaseadministratorCommented:
GPO:
Computer -> admin templates -> System -> Windows time sercive -> time providers
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
From an elevated command prompt on your PDCe:

w32tm /config /syncfromflags:manual "/manualpeerlist:0.ca.pool.ntp.org,0x1 1.ca.pool.ntp.org,0x1 2.ca.pool.ntp.org,0x1 3.ca.pool.ntp.org,0x1" /reliable:yes [Enter]

w32tm /config /update [Enter]

net stop w32time && net start w32time [Enter]

w32tm /resync /force [Enter]

w32tm /query /source [Enter]

Your response to this one should be: 1.ca.pool.ntp.org (or other). This will set your PDCe as authoritative time source for the domain which is what it is supposed to be.

Check your SCOPE OPTIONS in DHCP to see if NTP has been set to the DHCP server and remove that setting.

www.ntp.org is where to find your local servers as the above server settings are for our Canadian ones.

Philip
0
 
Radhakrishnan RITCommented:
Hi,

Refer this MS article http://support.microsoft.com/kb/816042/ which should fix your issue.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
iNetSystemAuthor Commented:
A bit confused on the solutions.

NTP is on the DC under DHCP Options and is fine, I wouldn't want to remove it.
Are you suggesting if I manually correct the PDC time that all member servers will automatically catch up?
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
The PDC is the "authoritative" time source but all other Domain Controllers get that Time source from the PDC and distribute the time to the clients. Depending on the DC the client is authenticating from that is the time source where that PC is getting it from.

If your clients are getting there time source from a DC that is not holding the PDC role this is normal and it is setup this way to distribute the load among the DC's.

You can check what DC you are authenticate to by doing the following..
- open cmd
- type: set logonserver

That command will tell you what DC you are authenticating to which will also be the server your machine is getting its time source from (unless harden in the registry or settings from the DHCP).

As already listed above you can resync your client/server using the w32tm /resync command. If you need to continue to do this then there might be something wrong with the client/server in regards to the trust on the domain.

I personally would not recommend hardening the PDC server in the registry as it should distribution among all the DC's in the environment.

If a machine is out of sync and you resync it using the w32/tm command depending on how far off the time is it will not resync instantly and is a gradual process.

Will.
0
 
Felix LevenSenior System and DatabaseadministratorCommented:
Hi, do you need more assistance on this Topic ?
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

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