Re: ISA Server 2004 and External Time Source

Kevin,

Thanks for your email. I have since tried 5 different NTP servers and all 5
are giving me errors, on the w32tm /resync command prompt I get "The computer
did not resync because no time data was available", and in the event log I
get Event ID 38 telling me that "The time provider Ntpclient cannot reach or
is currently receiving invalid tima data from xx.xx.xx.xx (address of my ntp
server)".

In ISA Server 2004 there is an SBS Localhost Access Rule which lists NTP
(UDP) as one of it's protocols. This rule is an Allow rule and the NTP
Protocol is using port 123 to send and receive. Plus, I have looked at the
Logging in ISA Server 2004 as requested by someone else on the forum, and
there are no errors on opening up port 123 that I can see in there.

Any ideas on this would be appreciated ....

"Kevin Longley" wrote:

Can you tell us exactly how your rules are configured for NTP?

"Ripley" <Ripley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F967556A-C3B1-4398-816E-7A2AD3BE7408@xxxxxxxxxxxxxxxx
I am running SBS 2003 Premium with ISA Server 2004 installed. All client
computers get their time from the DC as normal. But I want to setup an
external time source, so that the DC gets it's time synchronised across
the
internet.

I found an NTP Server, and have it's IP address and FQDN name. I then read
the SBS article (http://www.isaserver.org/articles/sbstimesync.html) about
how to configure SBS and ISA. However, the article related to ISA Server
2000. I managed to find the NTP Protocol in ISA Server 2004 and it *seems*
ok, using UDP port 123. I can also see a SBS LocalHost Access Rule where
it
seems to be using this protocol. I really have no idea if these settings
are
right or not though.
After settin up all the registry settings though, I'm getting Event ID 38
and 47 reporting that the data being received from my NTP server is
invalid.
I also cannot ping the IP address of my NTP server. I'm guessing I've
missed
something somewhere in perhaps the ISA Server 2004 setup??

Can anyone shed any light on this?



.

Relevant Pages

  • Re: Problem with updates
    ... I did setup the Auto Discovery using wpad but when I tell the client ... specific name of the ISA server it communicates with it immediatly. ... *outbound* Protocol, so don't get hung up on that idea. ...
    (microsoft.public.isa.configuration)
  • Re: Help a Noobie please with opening a port
    ... Unless the WARP client is making CERN proxy requests, ... 'Selected Protocols' and created a new protocol using Port range ... LocalHost or Internal (if on other server) ... Microsoft ISA Server Partners: Partner Hardware Solutions ...
    (microsoft.public.isaserver)
  • Re: Help a Noobie please with opening a port
    ... assume a Computer Set would also work since it also uses the IP#? ... 'Selected Protocols' and created a new protocol using Port range ... LocalHost or Internal (if on other server) ... Microsoft ISA Server Partners: Partner Hardware Solutions ...
    (microsoft.public.isaserver)
  • Re: ISA Server 2004 and External Time Source
    ... the filter to only show traffic from the SBS. ... Troubleshooting Client Authentication on Access Rules in ISA Server 2004 ... Deployment Guidelines for ISA Server 2004 Enterprise Edition ... I found an NTP Server, and have it's IP address and FQDN name. ...
    (microsoft.public.isa)
  • Re: Publishing Direct Connect (DC++)
    ... I know nothing about DC++ - if it has any protocol ... access to the server sitting behind it, so it's just inbound from elsewhere. ... to the main HUB from behind my ISA server. ... DC++ TCP Port 411 ...
    (microsoft.public.isa.publishing)