Thanks! Now that we've confirmed I have only a vague idea of what I'm doing here...
What is the difference in having a PDC-Emulator having its parameter set for NT5D5 (as is mine) and NTP? What do the flags do here? Finally (and hopefully!), when going back to fix what I've been breaking for several months... Once the PDC-Emulator is syncing with the external source properly, how should the WTime32 parameters be set in all the other servers (including the other local DCs as well as "member servers" so they will: 1. Sync with the PDC-Emulator and this sytem only? 2. Not themselves try to act as local time servers? If the PDC-Emulator happens to go down, does one then try to establish that FSMO role to one of the other DCs (to keep time sync services available)? Thanks y'all for your patience! -- Richard D. McClary Systems Administrator, Information Technology Group ASPCA® 1717 S. Philo Rd, Ste 36 Urbana, IL 61802 [email protected] P: 217-337-9761 C: 217-417-1182 F: 217-337-9761 www.aspca.org The information contained in this e-mail, and any attachments hereto, is from The American Society for the Prevention of Cruelty to Animals® (ASPCA ®) and is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying or use of the contents of this e-mail, and any attachments hereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by reply email and permanently delete the original and any copy of this e-mail and any printout thereof. "Maglinger, Paul" <[email protected]> wrote on 09/21/2009 02:43:33 PM: > Found it. We have 2 Windows NTP servers. One hadn't been changed > from NT5D5 to NTP, and the AnnounceFlags hadn't been changed from 10 > to 5. Will look at everything tomorrow and see if things have sync'd up. > > -----Original Message----- > From: Maglinger, Paul [mailto:[email protected]] > Sent: Monday, September 21, 2009 2:36 PM > To: NT System Admin Issues > Subject: RE: Why is Windows Time service crap? > > Let me do some poking around... > > -----Original Message----- > From: Steven M. Caesare [mailto:[email protected]] > Sent: Monday, September 21, 2009 1:50 PM > To: NT System Admin Issues > Subject: RE: Why is Windows Time service crap? > > Multiple Windows machine are exactly 24 seconds behind multiple UNIXmachines? > > -sc > > > -----Original Message----- > > From: Maglinger, Paul [mailto:[email protected]] > > Sent: Monday, September 21, 2009 10:21 AM > > To: NT System Admin Issues > > Subject: RE: Why is Windows Time service crap? > > > > I set up redundant time servers. When I do a ntpq -p on all the Unix > > servers, everything is in line with each other. It appears the Windows > > servers are the ones that are off. > > > > -----Original Message----- > > From: Steven M. Caesare [mailto:[email protected]] > > Sent: Monday, September 21, 2009 8:02 AM > > To: NT System Admin Issues > > Subject: RE: Why is Windows Time service crap? > > > > Do you know for a fact that your UNIX box is not 24 seconds ahead? > > > > -sc > > > > > -----Original Message----- > > > From: Maglinger, Paul [mailto:[email protected]] > > > Sent: Monday, September 21, 2009 8:56 AM > > > To: NT System Admin Issues > > > Subject: RE: Why is Windows Time service crap? > > > > > > I have Windows and Unix boxes pointing to the same sources, yet my > > > Windows box is consistantly 24 seconds behind. > > > > > > -----Original Message----- > > > From: Kurt Buff [mailto:[email protected]] > > > Sent: Friday, September 18, 2009 6:54 PM > > > To: NT System Admin Issues > > > Subject: Re: Why is Windows Time service crap? > > > > > > I set both of my DCs in the HQ to sync to us.pool.ntp.org, and have > > no > > > issues. > > > > > > On Fri, Sep 18, 2009 at 07:36, <[email protected]> wrote: > > > > > > > > Greetings! > > > > > > > > I have workstations and servers in my domain whose time is all over > > > the > > > > place! > > > > > > > > Two servers I manually sync'd with a domain controller less than 24 > > > hours > > > > ago are now once again 3 minutes behind. > > > > > > > > Workstations are up to 5 minutes one way or the other. > > > > > > > > I know this keeps coming up here, but again, please... > > > > > > > > 1. With multiple domain controllers, does one pick one of them, > > sync > > > to an > > > > outside time source, then somehow point the other DCs to this DC? > > If > > > so, > > > > then one puts in the name of the selected DC in the registry > > settings > > > for > > > > time services? OR, does one make sure all the DCs point to the > > same > > > > external NTP server? > > > > > > > > 2. Why do servers and workstations drift off, time-wise? How to > > stop > > > this? > > > > -- > > > > Richard D. McClary > > > > Systems Administrator, Information Technology Group > > > > > > > > ASPCA® > > > > 1717 S. Philo Rd, Ste 36 > > > > Urbana, IL 61802 > > > > > > > > [email protected] > > > > > > > > P: 217-337-9761 > > > > C: 217-417-1182 > > > > F: 217-337-9761 > > > > www.aspca.org > > > > > > > > > > > > The information contained in this e-mail, and any attachments > > hereto, > > > is > > > > from The American Society for the Prevention of Cruelty to Animals® > > > (ASPCA®) > > > > and is intended only for use by the addressee(s) named herein and > > may > > > > contain legally privileged and/or confidential information. If you > > > are not > > > > the intended recipient of this e-mail, you are hereby notified that > > > any > > > > dissemination, distribution, copying or use of the contents of this > > > e-mail, > > > > and any attachments hereto, is strictly prohibited. If you have > > > received > > > > this e-mail in error, please immediately notify me by reply email > > and > > > > permanently delete the original and any copy of this e-mail and any > > > printout > > > > thereof. > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
