Guest JR Posted February 26, 2008 Posted February 26, 2008 Hello folks I've got a big problem. We have a Server 2003 controlling our network (AD inside). The folks that installed it (and which I can't contact...) set it up so it would sync time with outside and then send that time to the rest of the network. Problem is, the clock is permanently 8 minuts late! I know that, when they set this up, they ran a registry "patch" with the following code (I've replaced the server's name with OUR.SERVERNAME.DOMAIN.PP for this): [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config] "LastClockRate"=dword:0002625a "MinClockRate"=dword:000260d4 "MaxClockRate"=dword:000263e0 "FrequencyCorrectRate"=dword:00000004 "PollAdjustFactor"=dword:00000005 "LargePhaseOffset"=dword:02faf080 "SpikeWatchPeriod"=dword:00000384 "HoldPeriod"=dword:00000005 "LocalClockDispersion"=dword:0000000a "EventLogFlags"=dword:00000002 "PhaseCorrectRate"=dword:00000007 "MinPollInterval"=dword:00000006 "MaxPollInterval"=dword:0000000a "UpdateInterval"=dword:00000064 "MaxNegPhaseCorrection"=dword:ffffffff "MaxPosPhaseCorrection"=dword:ffffffff "AnnounceFlags"=dword:00000005 "MaxAllowedPhaseOffset"=dword:0000012c [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters] "ServiceMain"="SvchostEntry_W32Time" "NtpServer"="OUR.SERVERNAME.DOMAIN.PP,0x8" "Type"="NTP" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient] "Enabled"=dword:00000001 "InputProvider"=dword:00000001 "AllowNonstandardModeCombinations"=dword:00000001 "CrossSiteSyncFlags"=dword:00000002 "ResolvePeerBackoffMinutes"=dword:0000000f "ResolvePeerBackoffMaxTimes"=dword:00000007 "CompatibilityFlags"=dword:80000000 "EventLogFlags"=dword:00000001 "LargeSampleSkew"=dword:00000003 "DllName"="C:\\WINDOWS\\system32\\w32time.dll" "SpecialPollTimeRemaining"=hex(7):00,00 "SpecialPollInterval"=dword:0000012c [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer] "InputProvider"=dword:00000000 "AllowNonstandardModeCombinations"=dword:00000001 "DllName"="C:\\WINDOWS\\system32\\w32time.dll" "Enabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Enum] "0"="Root\\LEGACY_W32TIME\\0000" "Count"=dword:00000001 "NextInstance"=dword:00000001 I've tried setting up time sync following the instructions in: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/ws03mngd/26_s3wts.mspx#EBB both the registry entries AND the manual comand line use of 132tm but no luck... allways still late... Any ideas?
Guest Meinolf Weber Posted February 26, 2008 Posted February 26, 2008 Re: Syncronizing time: Server 2003 Hello JR, See your other posting and please do not multipost, use crossposting. One post to different groups and one answer, as a result, to the different groups makes it easier for everybody here. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > Hello folks > > I've got a big problem. We have a Server 2003 controlling our network > (AD inside). The folks that installed it (and which I can't > contact...) set it up so it would sync time with outside and then send > that time to the rest of the network. Problem is, the clock is > permanently 8 minuts late! > > I know that, when they set this up, they ran a registry "patch" with > the following code (I've replaced the server's name with > OUR.SERVERNAME.DOMAIN.PP for this): > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config] > "LastClockRate"=dword:0002625a > "MinClockRate"=dword:000260d4 > "MaxClockRate"=dword:000263e0 > "FrequencyCorrectRate"=dword:00000004 > "PollAdjustFactor"=dword:00000005 > "LargePhaseOffset"=dword:02faf080 > "SpikeWatchPeriod"=dword:00000384 > "HoldPeriod"=dword:00000005 > "LocalClockDispersion"=dword:0000000a > "EventLogFlags"=dword:00000002 > "PhaseCorrectRate"=dword:00000007 > "MinPollInterval"=dword:00000006 > "MaxPollInterval"=dword:0000000a > "UpdateInterval"=dword:00000064 > "MaxNegPhaseCorrection"=dword:ffffffff > "MaxPosPhaseCorrection"=dword:ffffffff > "AnnounceFlags"=dword:00000005 > "MaxAllowedPhaseOffset"=dword:0000012c > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Paramete > rs] > "ServiceMain"="SvchostEntry_W32Time" > "NtpServer"="OUR.SERVERNAME.DOMAIN.PP,0x8" > "Type"="NTP" > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProv > iders\NtpClient] > "Enabled"=dword:00000001 > "InputProvider"=dword:00000001 > "AllowNonstandardModeCombinations"=dword:00000001 > "CrossSiteSyncFlags"=dword:00000002 > "ResolvePeerBackoffMinutes"=dword:0000000f > "ResolvePeerBackoffMaxTimes"=dword:00000007 > "CompatibilityFlags"=dword:80000000 > "EventLogFlags"=dword:00000001 > "LargeSampleSkew"=dword:00000003 > "DllName"="C:\\WINDOWS\\system32\\w32time.dll" > "SpecialPollTimeRemaining"=hex(7):00,00 > "SpecialPollInterval"=dword:0000012c > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProv > iders\NtpServer] > "InputProvider"=dword:00000000 > "AllowNonstandardModeCombinations"=dword:00000001 > "DllName"="C:\\WINDOWS\\system32\\w32time.dll" > "Enabled"=dword:00000001 > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Enum] > "0"="Root\\LEGACY_W32TIME\\0000" > "Count"=dword:00000001 > "NextInstance"=dword:00000001 > I've tried setting up time sync following the instructions in: > > http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technol > ogies/security/ws03mngd/26_s3wts.mspx#EBB > > both the registry entries AND the manual comand line use of 132tm but > no luck... allways still late... > > Any ideas? >
Guest JR Posted February 26, 2008 Posted February 26, 2008 Re: Syncronizing time: Server 2003 On Tue, 26 Feb 2008 20:56:35 +0000 (UTC), Meinolf Weber <meiweb(nospam)@gmx.de> wrote: >Hello JR, > >See your other posting and please do not multipost, use crossposting. One >post to different groups and one answer, as a result, to the different groups >makes it easier for everybody here. > >Best regards > >Meinolf Weber Seen it, will try tomorrow, thanks a lot :) PS: I do know about the posting, but my news program is crap. Can't cross post with it...
Guest Meinolf Weber Posted February 26, 2008 Posted February 26, 2008 Re: Syncronizing time: Server 2003 Hello JR, I use this one: http://www.jetbrains.com/omea/reader/index.html Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > On Tue, 26 Feb 2008 20:56:35 +0000 (UTC), Meinolf Weber > <meiweb(nospam)@gmx.de> wrote: > >> Hello JR, >> >> See your other posting and please do not multipost, use crossposting. >> One post to different groups and one answer, as a result, to the >> different groups makes it easier for everybody here. >> >> Best regards >> >> Meinolf Weber >> > Seen it, will try tomorrow, thanks a lot :) > > PS: I do know about the posting, but my news program is crap. Can't > cross post with it... >
Recommended Posts