troubleshooting Question

ASA 5510, PIX 506e IPSec Site-to-Site, one end not default gateway

Avatar of pboustani
pboustaniFlag for Canada asked on
VPNInternet Protocol SecurityCisco
1 Comment1 Solution554 ViewsLast Modified:
Hi, we're looking to create a site to site tunnel from our ASA 5510 at our office to our Pix 506e at our Co-lo facility. The trick is the Pix at the co-lo is not the default gateway for our co-located servers. Our co-lo does managed firewalling, and thus they are the default gateway for the "public" network. Each of our servers has a second NIC on a "Private" network, and this is the network that the Pix is on. Up until now each of us VPN directly from our PC to the Pix and are given access to the private network at our Co-lo. It works great, but we want to move to a tunnel. I assume our Pix is acting like any regular VPN appliance (watchdog/windows vpn/etc) and doing NAT. So thus the clients are able to communicate with the server.

But as I understand it, an IPSec tunnel is routed, so how do we go about doing this? We DID manage to get a successful site-to-site tunnel going, but no traffic would pass. Phase 1 and 2 were successful and both ends showed an IPSec/IKE connection.

Any help would be appreciated. Or did we just miss a setting? But I think it has to do with the fact the Pix is not the default gateway at our Co-lo.


P.S. Looking to have this up and running this week. 500 Points.
Les Moore
Systems Architect
Join our community to see this answer!
Unlock 1 Answer and 1 Comment.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 1 Comment.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros