![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Windows NT/2000/2003 Server/2008 Server Find support for Windows NT/2000/2003 Server/2008 Server editions. |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) | |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Clock Sync issues
Quote:
This is from the PDC (only DC in the domain) it needs to be configured as a reliable time source and set up to sync with an external NTP. *I did notice in the registry the NTP client is enabled, does that need to be disabled for the time sync to work? When I set up the computer to sync with an external time source and run the "w32tm /resync" command it returns "no time data available" ANY IDEAS!! My clocks are out of wack!!!
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
| Sponsored Links |
|
|
#2 (permalink) |
|
Registered User
Join Date: Oct 2004
Location: Omaha, The Center of the Universe
Posts: 7,632
OS: WinXP, Win2K3
|
Re: Clock Sync issues
The way I usually set the DC time source is through the cmd prompt.
C:\>net time /setsntp:time.windows.com then you have to stop the time service C:\>net stop w32time then you have to start it back up C:\>net start w32time I have noticed that the time.windows.com site is not always reliable and started to use a different time server. time.nist.gov |
|
|
|
|
|
#3 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
The NTP Server has been set as <69.222.103.98>. I have followed your directions or ones similar to it. Here is a list of NTP servers however most of them are not responding to ping commands.
http://tf.nist.gov/timefreq/service/time-servers.html Which NTP should I use? This is the only DC in the domain, how can i initiate a time sync from the command line using the given NTP?
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#4 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
The PDC needs to be declared an authoritative time source, which I am almost certain has already happened (all domain clients are syncing with the PDC).
So really the only thing I need to accomplish is to get the PDC syncing with an external time source. As stated before I have followed you steps and the NTP was set, however even though the service is stopped and restarted, the clock on the PDC is not accurate (not syncing with NTP). I need to verify the accuracy of NTP <69.222.103.98>. What is the command for initiating the sync with the given NTP? Thanks.
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#6 (permalink) |
|
Registered User
Join Date: Oct 2004
Location: Omaha, The Center of the Universe
Posts: 7,632
OS: WinXP, Win2K3
|
Re: Clock Sync issues
I got mine to change time servers but it's not getting the info for the site.
I'm digging into this a little more. Maybe it's the stupid DST change that screwed this all up. |
|
|
|
|
|
#8 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
C:\>net time /setsntp:time-a.timefreq.bldrdoc.gov
Does the NTP need the suffix x0x on it when doing it from the command line? then start and stop services? The clock should now be in sync?
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#10 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
Joe,
Followed the steps, even putting the 0x1 at the end of the NTP server string (regedit). Still the PDC clock remains out of sync. I did read the it can take up to an hour to fully sync, however that can be avoided by typing w32tm /resync when I run that it returns "No Time Data Was Available".
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#12 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
It shows nothing as a result of the sync failure, I see about every couple of hours the same message as seen earlier in this thread.
I am following the steps here right now. http://support.microsoft.com/kb/929276 Let me know if you think of anything. Thanks.
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#13 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
This must either have something to do with a firewall or DST 2007.
What are the ports for NTP? I don't run a local firewall, but Symantec AV server is running. How should I open them if they were to be blocked?
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#14 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
This is a Group Policy issue...still waiting to configure policies correctly...looks promising.
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#15 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
The following is a GPRESULT on the DC with the error. Do these settings look correct?
FrequencyCorrectRate 4 HoldPeriod 5 LargePhaseOffset 1280000 MaxAllowedPhaseOffset 300 MaxNegPhaseCorrection 54000 MaxPosPhaseCorrection 54000 PhaseCorrectRate 1 PollAdjustFactor 5 SpikeWatchPeriod 90 UpdateInterval 30000 General Parameters AnnounceFlags 10 EventLogFlags 2 LocalClockDispersion 10 MaxPollInterval 15 MinPollInterval 10
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
|
|
#16 (permalink) |
|
Member, Networking Team
Join Date: Jan 2005
Location: Ohio
Posts: 1,040
OS: Windows Server 2003
|
Re: Clock Sync issues
All:
This issue was resolved by configuring the group policy. The Default Domain Policy had been configured to NTP Client type "NTP" rather than "NT5DS" which was restricting every computer on the domain, inluding the server from from accessing "out of domain" time servers. Here is a good link describing the policies. http://www.microsoft.com/technet/pro.../26_s3wts.mspx Thanks.
__________________
Because you can read this thank a teacher, because it's English thank a soldier. |
|
|
|
![]() |
| Thread Tools | |
|
|