Re: W32 time problem on SBS2003 Premium
- From: "jjjdavidson" <jjjdavidson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Jul 2005 06:05:03 -0700
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.
> > > > >> >
> > > >
> > > >
> > > >
.
- Follow-Ups:
- Re: W32 time problem on SBS2003 Premium
- From: wedor
- Re: W32 time problem on SBS2003 Premium
- From: wedor
- Re: W32 time problem on SBS2003 Premium
- From: Ken-T
- Re: W32 time problem on SBS2003 Premium
- References:
- W32 time problem on SBS2003 Premium
- From: Ken-T
- RE: W32 time problem on SBS2003 Premium
- From: jjjdavidson
- RE: W32 time problem on SBS2003 Premium
- From: Ken-T
- Re: W32 time problem on SBS2003 Premium
- From: wedor
- Re: W32 time problem on SBS2003 Premium
- From: Ken-T
- Re: W32 time problem on SBS2003 Premium
- From: jjjdavidson
- Re: W32 time problem on SBS2003 Premium
- From: Ken-T
- W32 time problem on SBS2003 Premium
- Prev by Date: Re: Very frustrated with MS Server 2003 SBS
- Next by Date: Re: Dcpromo + Certificate services
- Previous by thread: Re: W32 time problem on SBS2003 Premium
- Next by thread: Re: W32 time problem on SBS2003 Premium
- Index(es):
Relevant Pages
|