RE: NTP Rule for DC doesn't work
- From: "blueboy1894" <blueboy1894@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Jun 2005 00:41:04 -0700
Hi
Still searching for a solution to this one.
I can get the ISA to sync externally but I know that's not right - the DC
should be the authoritative time source but I can't get it to talk to an
external ntp server.
I need to get this working or my entire project will grind to a halt so any
advice would be much appreciated...
"blueboy1894" wrote:
> Hi
>
> I'm trying to get my win2003 dc to sync with an external time source. All
> the other servers are set to nt5ds (sync using domain hierarchy), as per
> default behaviour.
>
> The access rule in the firewall is as follows:
>
> To: (computer object with ip of external ntp)
> From: (computer object representing the dc)
> Protocol: NTP(UDP)
> All Users
>
> The dc resolves the address of the ntp server but can't connect. I've tried
> this all sorts of different ways including allowing 2-way comms between the
> two hosts.
>
> The isa 2004 logging screen reports outbound traffic on NTP(UDP) to the ntp
> server's ip and then a "Denied Connection" action, but without any rule name.
>
> The network is in a standard back-to-back DMZ with dual-homed ISA in front
> of the servers, and a WatchGuard firebox further out sitting between the
> Internet router and the ISA. The WG allows NTP.
>
> I've tried to solve this for 2 days and got nowhere! Any help much
> appreciated...
.
- References:
- NTP Rule for DC doesn't work
- From: blueboy1894
- NTP Rule for DC doesn't work
- Prev by Date: allowing MSN Messenger 7 video and audio to work on pc behind isa
- Next by Date: ISA 2004 with 3rd party load balancing solution?
- Previous by thread: NTP Rule for DC doesn't work
- Next by thread: re:NTP Rule for DC doesn't work
- Index(es):
Relevant Pages
|