Re: Setting Up SBS to Sync w/ External Time Source



No. I am not using ISA. We use an external piece of hardware.

Thanks.


"clevere1" <noway@xxxxxxxxx> wrote in message
news:OSg2uMoRFHA.356@xxxxxxxxxxxxxxxxxxxxxxx
> Are you using ISA? If so make sure the NNTP port is setup for TCP not
> UDP..
>
> "epigram" <nospam@xxxxxxxxxx> wrote in message
> news:1114083905.f12ce4820134842ed203b53798ab574c@xxxxxxxxxxxx
>> Through some suggestions I found in this newsgroup and on the Internet, I
>> used the following to setup time synchronization between my XP Pro SP2
>> client PCs and my my SBS 2003 server. The server is synching with an
>> external time source.
>>
>> Here are the commands I ran on the server:
>>
>> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
>> net stop w32time
>> net start w32time
>> w32tm /resync
>>
>> Here are the commands I ran on the clients:
>>
>> net time /setsntp:<MY_SERVER>
>> w32tm /resync /nowait
>>
>>
>> This seemed to work, but about two days later I received the following
> event
>> in the SBS 2003 System Event Log:
>>
>> Type: Error
>> Source: W32Time
>> Event ID: 46
>> Description: The time service encountered an error and was forced to shut
>> down. The error was: 0xC0020018
>>
>> From then on I started getting this sequence of Info, Warning, Error
> events
>> 1 to 3 times a day:
>>
>> Type: Information
>> Source: W32Time
>> Event ID: 38
>> Description: The time provider NtpClient cannot reach or is currently
>> receiving invalid time data from <MY_SERVER>
>> (ntp.m|0x0|10.0.0.3:123->10.0.0.3:123).
>>
>> Type: Warning
>> Source: W32Time
>> Event ID: 47
>> Description: Time Provider NtpClient: No valid response has been received
>> from manually configured peer <MY_SERVER> after 8 attempts to contact
>> it.
>> This peer will be discarded as a time source and NtpClient will attempt
>> to
>> discover a new peer with this DNS name.
>>
>> Type: Error
>> Source: W32Time
>> Event ID: 29
>> Description: The time provider NtpClient is configured to acquire time
> from
>> one or more time sources, however none of the sources are currently
>> accessible. No attempt to contact a source will be made for XX minutes.
>> NtpClient has no source of accurate time.
>>
>> XX varies from 15 to 960 minutes. Does anyone have an idea of what the
>> issue is here? Any help would be MUCH appreciated. Thanks!
>>
>>
>
>


.



Relevant Pages

  • Re: w32Time - External Source Sinc - HELP!!
    ... Got it, that functionallity is by design ISA default behaviour, my mistake ... Mi DC is a VPC hosted on Virtual Server 2005 R2. ... The time provider NtpClient is configured to acquire time from one ... This peer will be discarded as a time source and NtpClient will ...
    (microsoft.public.windows.server.active_directory)
  • RE: Setting Up SBS to Sync w/ External Time Source
    ... Looks like it lost the peer group and is trying to sync from itself as a time ... > client PCs and my my SBS 2003 server. ... > net start w32time ... > Description: Time Provider NtpClient: No valid response has been received ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting Up SBS to Sync w/ External Time Source
    ... I'm using ISA and having a similar problem. ... and should it be TCP or UDP? ... >> net start w32time ... The time provider NtpClient is configured to acquire time ...
    (microsoft.public.windows.server.sbs)
  • Re: w32tm will not synch on SBS 2000 server
    ... The main thing is that you need to create a filter in ISA. ... > am using the server as an internal timeserver for my domain. ... > The Windows Time service was stopped successfully. ... > W32Time: Advertising that I'm a Time Service Provider ...
    (microsoft.public.win2000.security)
  • Re: Incorrect time on server and PCs
    ... Event Source: W32Time ... The time provider NtpClient cannot reach or is currently receiving invalid ... Frank McCallister SBS MVP ... Do I run it only once on server or do I schedule it to run ...
    (microsoft.public.windows.server.sbs)