VPN

Hi,

I have a question about VPNs into a private network with different
security zones. All remote access clients have to access the part of the
private network where they are normally ocated. So some of the remote
clients shall access one zone, while others shall access other zones. My
question is: does ISA server support a scenario where one server
(probably the ISA-server) is located in the perimeter network and
receives all encapsulated requests from the remote clients. The VPN
traffic is unwrapped and inspected at the server before it is
encapsulated again with the destination address (found in the inner
packet) in the zone where the remote clients normally are located (when
at work). All zones will have a Remote Access Server to decrypt and
unwrap traffic from the server in the perimeter network. I do not know
if this will work, especially when it comes to the addressing issues,
and the encapsulation of packets at the server in the perimeter network.
I hope someone understands the problem, it is a little bit complex to
describe in text...

Any advice, suggestions or recommendations would be greatly appreciated!


Thanks,
Lill

Please don't keep posting the same question with a different subject,...it
becomes impossible to keep track of who answered what, when , and where.

I answered this in one of the other copies of this you posted.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"lill" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I have a question about VPNs into a private network with different
> security zones. All remote access clients have to access the part of the
> private network where they are normally ocated. So some of the remote
> clients shall access one zone, while others shall access other zones. My
> question is: does ISA server support a scenario where one server
> (probably the ISA-server) is located in the perimeter network and
> receives all encapsulated requests from the remote clients. The VPN
> traffic is unwrapped and inspected at the server before it is
> encapsulated again with the destination address (found in the inner
> packet) in the zone where the remote clients normally are located (when
> at work). All zones will have a Remote Access Server to decrypt and
> unwrap traffic from the server in the perimeter network. I do not know
> if this will work, especially when it comes to the addressing issues,
> and the encapsulation of packets at the server in the perimeter network.
> I hope someone understands the problem, it is a little bit complex to
> describe in text...
>
> Any advice, suggestions or recommendations would be greatly appreciated!
>
>
> Thanks,
> Lill
>
>
>