Time Servers
|
From: kj on 5 Mar 2007 14:27 Gary J. Dikkema wrote: > So... after running the various ...diag tools I now need a hotfix for > DNS as per eventid 4015 which I ma holding on the phone for. > > Well that's a turn in another direction that I wouldn't expect to fix the time wierdness. Presumming it doesn't, try these (on the server first); w32tm /dumpreg /subkey:parameters w32tm /dumpreg /subkey:config and post the settings. -- /kj
From: Gary J. Dikkema on 5 Mar 2007 14:39 And it did NOT work! Hers's the info... Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>w32tm /dumpreg /subkey:parameters Value Name Value Type Value Data -------------------------------------------------- ServiceMain REG_SZ SvchostEntry_W32Time ServiceDll REG_EXPAND_SZ C:\WINDOWS\system32\w32time.dll Type REG_SZ NTP NtpServer REG_SZ time.windows.com,0x8 C:\Documents and Settings\Administrator>w32tm /dumpreg /subkey:config Value Name Value Type Value Data ----------------------------------------------------------- LastClockRate REG_DWORD 99894 MinClockRate REG_DWORD 99894 MaxClockRate REG_DWORD 100394 FrequencyCorrectRate REG_DWORD 4 PollAdjustFactor REG_DWORD 5 LargePhaseOffset REG_DWORD 50000000 SpikeWatchPeriod REG_DWORD 900 HoldPeriod REG_DWORD 5 LocalClockDispersion REG_DWORD 10 EventLogFlags REG_DWORD 2 PhaseCorrectRate REG_DWORD 7 MinPollInterval REG_DWORD 6 MaxPollInterval REG_DWORD 10 MaxNegPhaseCorrection REG_DWORD -1 MaxPosPhaseCorrection REG_DWORD -1 UpdateInterval REG_DWORD 100 AnnounceFlags REG_DWORD 10 MaxAllowedPhaseOffset REG_DWORD 300 C:\Documents and Settings\Administrator> "kj" <kj(a)nowhere.com> wrote in message news:O8y4Px1XHHA.4868(a)TK2MSFTNGP03.phx.gbl... > Gary J. Dikkema wrote: >> So... after running the various ...diag tools I now need a hotfix for >> DNS as per eventid 4015 which I ma holding on the phone for. >> >> > > Well that's a turn in another direction that I wouldn't expect to fix the > time wierdness. > > Presumming it doesn't, try these (on the server first); > > w32tm /dumpreg /subkey:parameters > > w32tm /dumpreg /subkey:config > > and post the settings. > > -- > /kj >
From: kj on 5 Mar 2007 15:05 Gary J. Dikkema wrote: > And it did NOT work! > > Hers's the info... > > Microsoft Windows [Version 5.2.3790] > (C) Copyright 1985-2003 Microsoft Corp. > > C:\Documents and Settings\Administrator>w32tm /dumpreg > /subkey:parameters > Value Name Value Type Value Data > -------------------------------------------------- > > ServiceMain REG_SZ SvchostEntry_W32Time > ServiceDll REG_EXPAND_SZ C:\WINDOWS\system32\w32time.dll > Type REG_SZ NTP > NtpServer REG_SZ time.windows.com,0x8 > > > C:\Documents and Settings\Administrator>w32tm /dumpreg /subkey:config > > Value Name Value Type Value Data > ----------------------------------------------------------- > > LastClockRate REG_DWORD 99894 > MinClockRate REG_DWORD 99894 > MaxClockRate REG_DWORD 100394 OK, these stand out as different against a couple of Servers that I compared too. Both local samples showed default values. These weren't the discrepencies I was expecting. ??? Perhaps further investigation using the following; http://technet2.microsoft.com/WindowsServer/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx?mfr=true LastClockRate Registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config Version Windows XP and Windows Server 2003 This entry is maintained by W32Time. It contains reserved data that is used by the Windows operating system, and any changes to this setting can cause unpredictable results. The default value on domain members is 156250. The default value on stand-alone clients and servers is 156250. MaxClockRate Registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config Version Windows XP and Windows Server 2003 This entry is maintained by W32Time. It contains reserved data that is used by the Windows operating system, and any changes to this setting can cause unpredictable results. The default value for domain members is 155860. The default value for stand-alone clients and servers is 155860. MinClockRate Registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config Version Windows XP and Windows Server 2003 This entry is maintained by W32Time. It contains reserved data that is used by the Windows operating system, and any changes to this setting can cause unpredictable results. The default value for domain members is 155860. The default value for stand-alone clients and servers is 155860. -- /kj
From: Gary J. Dikkema on 5 Mar 2007 15:23 Did those, ran the .bat file; saw the time get set correctly and then a few secs later revert to the +3 to +4 minutes head.... Strange! FWIW, ran that same hotfix on my backup R2 box and it failed... "kj" <kj(a)nowhere.com> wrote in message news:eFJsTG2XHHA.4220(a)TK2MSFTNGP03.phx.gbl... > Gary J. Dikkema wrote: >> And it did NOT work! >> >> Hers's the info... >> >> Microsoft Windows [Version 5.2.3790] >> (C) Copyright 1985-2003 Microsoft Corp. >> >> C:\Documents and Settings\Administrator>w32tm /dumpreg >> /subkey:parameters >> Value Name Value Type Value Data >> -------------------------------------------------- >> >> ServiceMain REG_SZ SvchostEntry_W32Time >> ServiceDll REG_EXPAND_SZ C:\WINDOWS\system32\w32time.dll >> Type REG_SZ NTP >> NtpServer REG_SZ time.windows.com,0x8 >> >> >> C:\Documents and Settings\Administrator>w32tm /dumpreg /subkey:config >> >> Value Name Value Type Value Data >> ----------------------------------------------------------- >> >> LastClockRate REG_DWORD 99894 >> MinClockRate REG_DWORD 99894 >> MaxClockRate REG_DWORD 100394 > > OK, these stand out as different against a couple of Servers that I > compared too. Both local samples showed default values. These weren't the > discrepencies I was expecting. ??? > > Perhaps further investigation using the following; > http://technet2.microsoft.com/WindowsServer/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx?mfr=true > > LastClockRate > Registry path > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config > > Version > Windows XP and Windows Server 2003 > > This entry is maintained by W32Time. It contains reserved data that is > used by the Windows operating system, and any changes to this setting can > cause unpredictable results. The default value on domain members is > 156250. The default value on stand-alone clients and servers is 156250. > > MaxClockRate > Registry path > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config > > Version > Windows XP and Windows Server 2003 > > This entry is maintained by W32Time. It contains reserved data that is > used by the Windows operating system, and any changes to this setting can > cause unpredictable results. The default value for domain members is > 155860. The default value for stand-alone clients and servers is 155860. > > MinClockRate > Registry path > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config > > Version > Windows XP and Windows Server 2003 > > This entry is maintained by W32Time. It contains reserved data that is > used by the Windows operating system, and any changes to this setting can > cause unpredictable results. The default value for domain members is > 155860. The default value for stand-alone clients and servers is 155860. > -- > /kj > >
From: kj on 5 Mar 2007 15:54
Gary J. Dikkema wrote: > Did those, ran the .bat file; saw the time get set correctly and then > a few secs later revert to the +3 to +4 minutes head.... > > Strange! > > FWIW, ran that same hotfix on my backup R2 box and it failed... You changed the registry settings back to default and ran a bat file previously posted? ( I'm confused) Are the reg settings still at default or back to the ones you had originally? .... ah, the DNS hotfix? -- /kj |