Re: DMZ to Internal problem
- From: "Vakharia" <Vakharia@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 May 2005 05:49:07 -0700
Hey Martijn,
I am not sure if you have got your answer or no. Neither do I wish to
comment on the design.
ISA has some other rules which are defined along with the explicit rules
that you define. This is the System Policy. I suspect that there is something
in there that may be coming in the way.
Vakharia
"Martijn" wrote:
> Thanx for this useless answer. But what I'm asking is how to get it to work.
> I don't need to know that it's a flawed design.
>
> I'm trying to setup a Exchange 2003 Front-End Server (This usually is
> located in the DMZ), but it seems that during the setup I need to use RPC,
> which by default is not allowed by the ISA 2004 firewall. How can I setup a
> situation that allows all traffic between the DMZ and the internal network?
> Without interferance of any kind.
>
>
>
> "A.Klimkin" <aklimkin at mail dot ru> schreef in bericht
> news:%23WIIS5XSFHA.3988@xxxxxxxxxxxxxxxxxxxxxxx
> > You've got flawed newtwork design here. You shouldn't place in DMZ any
> > trusted resource. DMZ is *untrusted* network. That is the whole idea of
> > DMZs. If the host should be a part of your domain, so place it on the LAN
> > side of the firewall and use server publishing to share its services (like
> > web, mail or so) with internet.
>
>
>
.
- Prev by Date: REdireting Port 80 HTTP traffic in isa2000 to a particular gateway
- Next by Date: Re: DNS Server does not answer "nslookup" on ISA Server 2004
- Previous by thread: REdireting Port 80 HTTP traffic in isa2000 to a particular gateway
- Next by thread: Re: DNS Server does not answer "nslookup" on ISA Server 2004
- Index(es):
Relevant Pages
|
