Solved

Passing traffic from ISA int/ext interfaces to a VPN device

Posted on 2008-10-09
3
736 Views
Last Modified: 2012-05-05
We currently have the following network setup

INTERNET
|
Router (external IP)
|
ASA (external IP on OUTSIDE interface and an internal IP on the INTERNAL interface - doing NAT)
|
ISA 2006 EE (internal IP on both interal/external interfaces - using ROUTE)
|
L3 Switches w/ intervlan routing - with the ISA IP as default gateway of the L3 switches

Basically we have a Site-To-Site VPN terminated on the Cisco ASA. If we connect the L3 switch and set the default gateway to the internal ip address of the Cisco ASA, the VPN is working fine - so from the VPN point of view everything is fine. When we try to access the VPN through the ISA (as a gateway) it gives out: - 0xc004002d FWX_E_UNREACHABLE_ADDRESS.

VPN network (of other peer) - 192.168.101.0/24

ASA internal IP address - 192.168.1.10/24

ISA external IP address - 192.168.1.20/24 (default gateway set to 192.168.1.10)
ISA internal IP address - 192.168.2.20/24

L3 Switch - 192.168.2.10/24 - (which links the internal interface of the ISA) (default gateway set to 192.168.20.20)
L3 Switch - 192.168.20.10/24 - (gateway ip address for the 192.168.20.0 network)
Workstation accessing the VPN - 192.168.20.2/24

From the ISA I have configured a static persistent-route to route 192.168.101.0/24 to 192.168.1.10 (ASA IP). Also there is a Network Rule inside the ISA to - route - from 192.168.1.20.0/24 to 192.168.101.0/24.
Also there is an access list for this.

Basically all the traffic (which includes CIFS etc.. (everything)) which is addressed to the other site (192.168.101.0/24) has to pass through the ISA internal -> external interfaces without getting blocked and it should just - route - it to the ASA.

Can someone help out on this problem? Or point out what exactly needs to be done to allow such traffic to pass through the ISA?

Thank you!

0
Comment
Question by:TylerDu
3 Comments
 
LVL 51

Accepted Solution

by:
Netman66 earned 500 total points
ID: 22717337
You need the ASA inside the ISA server.

Then you publish the VPN server (the ASA) in ISA.

What I see happening is that the ISA isn't seeing the ASA network as Trusted and it's also double-NAT'd this way.

Don't do NAT on the ASA.  Set it up as your VPN endpoint then you publish it in ISA server.

0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
Common practice undertaken by most system administrators is to document the configurations and final solutions of anything performed by them for their future use and reference. So here I am going to explain how to export ISA Server 2004 Firewall pol…
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now