Re: W32 time problem on SBS2003 Premium

That other server isn't really so odd. If the settings are "not configured",
then group policy isn't being applied and your manual settings will be used.
GP only applies if a setting is "enabled" or "disabled".

I'm glad to hear this might have solved your problem. I should have pointed
out the distinction between domain policy and DC policy myself. It took me a
while to figure out that the Client Computer GPO applied to the server as
well as workstations, unless a DC GPO overrides it.

"wedor" wrote:

> Good call, for some unexplained reason the NTP Client policy was set to
> "disabled" on this server, I re-enabled it and enabled the other policy
> settings as well and now it works!
>
> I have been fighting this for months so you get a very big thanks from me.
>
> The odd thing is on at least one other server the policies are "not
> configured" and the time service works fine there.
>
> "jjjdavidson" <jjjdavidson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:09C6EEA9-E95D-49B4-89EF-32F384B41B30@xxxxxxxxxxxxxxxx
> > I'm no expert on group policy myself, so I'm not sure where you're
> > looking.
> > The settings I've found sound similar. Under Computer Configuration /
> > Administrative Templates / System / Windows Time Service / Time Providers
> > you
> > have settings for Enable NTP Client, Configure NTP Client, and Enable NTP
> > Server. Are those what you're looking at?
> >
> > They can be "enabled", "disabled", or "not configured". Check the RSOP on
> > your server. If NTP Client is disabled, then the computer won't
> > synchronize
> > with a time source. If NTP Server is disabled, then other computers can't
> > synchronize to the server. The RSOP won't show anything that's "not
> > configured", and manual settings will take effect.
> >
> > "Ken-T" wrote:
> >
> >> Good question.... should have thought of looking there.
> >> Am no expert with group policies, but what I find is :
> >>
> >> Under "Domain controllers"
> >> Time Service - Active
> >> Time Service/Timeserver
> >> -WindowsNTP Client activeation -inactive
> >> -Windows NTP Client config -inactive
> >> -Windows NTP server activation -active
> >>
> >> Same keys show under Group policy objects, Default dom ctrls policy
> >>
> >>
> >> Erm.... could it be that the setting for NTP client inactive is causing
> >> all
> >> the problems??
> >>
> >> If so - could use some help with exactly which group policy settings to
> >> edit.
> >>
> >>
> >>
> >>
> >> "jjjdavidson" wrote:
> >>
> >> > Something else you might check: Do you have a domain group policy
> >> > defined
> >> > that specifies NTP servers?
> >> >
> >> > "Ken-T" wrote:
> >> >
> >> > >
> >> > > May be time to consider an alternative. Would appreciate any input
> >> > > here.
> >> > >
> >> > > The real problem is that after 24 hours W32Time stops issuing time to
> >> > > any
> >> > > domain clients that log in.
> >> > > I could install a freeware NTP client and have it auto-update the
> >> > > server
> >> > > time at set intervals to ensure system clock is ok (have tested one,
> >> > > worked
> >> > > fine).
> >> > > Is there then a way to stop W32Time trying to synch with an external
> >> > > time
> >> > > source and quitting after 24 hours - but keeping the W32Time service
> >> > > issuing
> >> > > time to domain clients that log in?
> >> > > Something like disabling the NTP "client" part that gets the time
> >> > > from
> >> > > external - but keeping the NTP Server running?
> >> > > Is such a thing possible at all.
> >> > >
> >> > > Ken
> >> > >
> >> > > "wedor" wrote:
> >> > >
> >> > > > I have the same problem with one server, it would be nice to find
> >> > > > an answer.
> >> > > >
> >> > > > "Ken-T" <KenT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> > > > news:7FB190AA-CA2B-499C-9895-7A6B433D0751@xxxxxxxxxxxxxxxx
> >> > > > > Thanks for the input,
> >> > > > >
> >> > > > > HKLM\System\CurrentControlSet\Services\W32Time\Parameters/Type is
> >> > > > > set to
> >> > > > > NTP
> >> > > > > NtpServer Param is currently set to time.windows.com,0x1
> >> > > > > (Am testing this after reading
> >> > > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;816042#XSLTH3163121123120121120120 )
> >> > > > >
> >> > > > > Have been trying up to now with NtpServer set as
> >> > > > > time.nist.gov,0x8 or
> >> > > > > ptbtime1.ptb.de,0x8. Even tried time.windows.com.
> >> > > > >
> >> > > > > Always with same results.
> >> > > > >
> >> > > > >
> >> > > > > Ken
> >> > > > >
> >> > > > > "jjjdavidson" wrote:
> >> > > > >
> >> > > > >> Under HKLM\System\CurrentControlSet\Services\W32Time\Parameters,
> >> > > > >> have you
> >> > > > >> made sure that Type is "NTP" instead of "NT5DS"? Something in
> >> > > > >> SBS keeps
> >> > > > >> resetting that on our server. While you're there, double-check
> >> > > > >> the
> >> > > > >> NtpServer
> >> > > > >> parameter.
> >> > > > >>
> >> > > > >> "Ken-T" wrote:
> >> > > > >>
> >> > > > >> >
> >> > > > >> > Am having the same problem with W32Time as others here.
> >> > > > >> > System is SBS2003 with SP1.
> >> > > > >> > Do not have ISA installed and have follwed the instructions at
> >> > > > >> > :
> >> > > > >> > http://www.smallbizserver.net/Default.aspx?tabid=142 to the
> >> > > > >> > letter.
> >> > > > >> > Have tried numerous time servers, am currently using
> >> > > > >> > ptbtime1.ptb.de
> >> > > > >> > which
> >> > > > >> > is working fine with our router. All outbound router ports are
> >> > > > >> > open.
> >> > > > >> >
> >> > > > >> > Command w32tm /resync always errors with could not be synced
> >> > > > >> > since no
> >> > > > >> > time
> >> > > > >> > available.
> >> > > > >> > After 24 hours the usual "The time service has not
> >> > > > >> > synchronized the
> >> > > > >> > system
> >> > > > >> > time for 86400 " etc etc in the log.
> >> > > > >> >
> >> > > > >> > If anyone out there has further ideas for fixing I would be
> >> > > > >> > very
> >> > > > >> > grateful.
> >> > > > >> >
> >> > > >
> >> > > >
> >> > > >
>
>
>
.

Relevant Pages

  • Re: Userenv Event ID 1054
    ... Did you add the slow link item to you policy or make another GPO ... To disable slow link detection on the SBS Server, ... please refer to the following settings to modify the ...
    (microsoft.public.windows.server.sbs)
  • Re: Inherited security properties
    ... group policy set on the organizational until that your server is in. ... settings at the local policy level. ... > When I look at the local security policy on the Windows ...
    (microsoft.public.win2000.security)
  • RE: Please help - with the portal server
    ... LAN settings - i was wondering may be - sps uses certain ports to communicate ... with the server over the internet. ... microsoft.sharepoint.portal.dll security permission grant set is incompatible ... Use Group Policy to Add the Sites ...
    (microsoft.public.sharepoint.portalserver)
  • Re: SBS DCOM
    ... On the server I was afraid to delete them ... (and I can now change policy settings and access DCOM and WMI ... |> steps to reset the group policy objects to default, ...
    (microsoft.public.windows.server.sbs)
  • Re: W32 time problem on SBS2003 Premium
    ... for some unexplained reason the NTP Client policy was set to ... The odd thing is on at least one other server the policies are "not ... > The settings I've found sound similar. ... > have settings for Enable NTP Client, Configure NTP Client, and Enable NTP ...
    (microsoft.public.windows.server.sbs)