Yes, vbiserver_01 is a PDC and it is configured to get time from an external
source. These are my registry settings for Config, Parameters,
TimeProviders\NtpClient, and TimeProviders\NtpServer
Value Name Value Type Value Data
-----------------------------------------------------------
LastClockRate REG_DWORD 156250
MinClockRate REG_DWORD 155860
MaxClockRate REG_DWORD 156640
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 3600
MaxPosPhaseCorrection REG_DWORD 3600
UpdateInterval REG_DWORD 100
AnnounceFlags REG_DWORD 5
MaxAllowedPhaseOffset REG_DWORD 300
FileLogSize REG_DWORD 268435456
FileLogName REG_SZ c:\windows\temp\w32time.log
FileLogEntries REG_SZ 0-116
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 pool.ntp.org,0x8
Value Name Value Type Value Data
----------------------------------------------------------------------
Enabled REG_DWORD 1
InputProvider REG_DWORD 1
AllowNonstandardModeCombinations REG_DWORD 1
CrossSiteSyncFlags REG_DWORD 2
ResolvePeerBackoffMinutes REG_DWORD 15
ResolvePeerBackoffMaxTimes REG_DWORD 7
CompatibilityFlags REG_DWORD -2147483648
EventLogFlags REG_DWORD 1
LargeSampleSkew REG_DWORD 3
DllName REG_SZ
C:\WINDOWS\system32\w32time.dll
SpecialPollTimeRemaining REG_MULTI_SZ
SpecialPollInterval REG_DWORD 3600
Value Name Value Type Value Data
----------------------------------------------------------------------
InputProvider REG_DWORD 0
AllowNonstandardModeCombinations REG_DWORD 1
DllName REG_SZ
C:\WINDOWS\system32\w32time.dll
Enabled REG_DWORD 1
"neo [mvp outlook]" wrote:
> Hmm... if vbiserver_01 is the PDC, is it configured to get time from an
> external source?
>
> "MEmerson" <(E-Mail Removed)> wrote in message
> news:271B6C19-E635-43C9-9587-(E-Mail Removed)...
> > No. Windows firewall is not enabled. I have also used Network Monitor to
> > verify the UDP message on port 123 is received by the server. Also I get
> > the
> > same behavior if I run "w32tm /monitor" on the server itself.
> >
> > "neo [mvp outlook]" wrote:
> >
> >> Anything between client/server that could be blocking udp port 123? (e.g.
> >> firewalls, acls on routers, .etc)
> >>
> >> "MEmerson" <(E-Mail Removed)> wrote in message
> >> news:147623CF-84F0-4236-8CBA-(E-Mail Removed)...
> >> >I am trying to get the NTP server working on windows server 2003 SP2. I
> >> >have
> >> > followed the instructions in KB 816042 "How to configure an
> >> > authoritative
> >> > time server in Windows Server 2003".
> >> > Running "netstat -an" returns
> >> > UDP 10.9.200.1:123 *:*
> >> > UDP 127.0.0.1:123 *:*
> >> > so NTP is listening on port 123.
> >> >
> >> > Running "w32tm /monitor" from anywhere on the domain returns
> >> > vbiserver_01.corp.vitalbasics.com *** PDC *** [10.9.200.1]:
> >> > ICMP: 0ms delay.
> >> > NTP: error ERROR_TIMEOUT - no response from server in 1000ms
> >> >
> >> > I turned logging on in the w32time registry settings and I am getting
> >> > the
> >> > following lines in the log when I run "w32tm /monitor"
> >> > 148660 17:40:31.0396834s - ListeningThread -- DataAvailEvent set for
> >> > socket
> >> > 0 (10.9.200.1:123)
> >> > 148660 17:40:31.0396834s - ListeningThread -- response heard from
> >> > 10.9.200.89:123
> >> > 148660 17:40:31.0396834s - Ignoring packet invalid mode combination
> >> > (in:3
> >> > out:0).
> >> >
> >> > I have the registry setting AllowNonstandardModeCombinations set to 1.
> >> >
> >>
> >>
> >>
>
>
>
|
Similar Threads
Linear Mode
