Re: ISA 2004 VPN Client can access DMZ but not Internal Domain
- From: "Binh Duong" <bduong1@xxxxxxx>
- Date: Mon, 13 Mar 2006 21:27:11 -0500
How is your ISA 2 configured? If you have internal and external conguration,
you will need to publish the internal domain to the DMZ.
hope this helps!
"FijianTribe" <FijianTribe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FB3D2FC7-5DDF-456B-B4E0-E32C4F848C90@xxxxxxxxxxxxxxxx
My setup looks like this:
(Internet) -> (ISA 1) -> (DMZ) -> (ISA 2) -> (Internal Domain)
ISA 1 & ISA 2 are two different machines. One serves as a front end and
the
other serves as the backed fire wall.
On my test DMZ I have a single machine that acts as a Domain
Controller/RADIUS Server/DNS/WINS/DHCP.
My VPN clients can authenticate and access all machines on the DMZ. They
also seem to see the ISA 2 server, and even resolve IP addresses for
machines
on the Internal domain.
The problem is that they cannot access any machines through the ISA2
server.
Any thoughts on where I can start? TechNet only seems to discuss the
solution for 2000 ISA.
.
- Prev by Date: Re: ISA 2004 SP2 WebProxy Filter Bug?
- Next by Date: ISA 2004 SP2 bug is FIXED
- Previous by thread: Re: Deep Packet Inspection
- Next by thread: Re: ISA 2004 VPN Client can access DMZ but not Internal Domain
- Index(es):
Relevant Pages
|