How do I configure a Cisco ASA 5505 to allow for outbound VPN traffic?

I'll qualify this question with a statement that I am NOT a network guy. I subcontract all substantial configuration settings to our office Ciscos 5505 units to someone who knows what they're doing.

Three years ago, some our guests in Office A were having trouble connecting their respective VPN client programs to their respective VPN servers (Cisco, Netscreen, Sonicwall, Checkpoint ...). My Cisco subcontractor at the time made some configuration changes to our ASA 5505 and the connectivity issues largely went away. It's important to note that the configuration settings made by my subcontractor had nothing to do with the VPN server functionality of the Office A ASA 5505. That was working fine. Instead, the configuration settings were simply designed to make Office A "friendlier" to VPN clients within our office attempting to connect to other VPN servers.

Segue forward three years. Some our guests in Office B are running into the same issues. My old Cisco subcontractor is unreachable, my new Cisco subcontractor is asking me what the old subcontractor did, and I, candidly, am not sure. I suggested that he poke around on the Office A ASA to try to determine what the old subcontractor did, but I'm not sure where he should poke.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mark AbbottCommented:
This can be caused by a variety of factors, and there aren't the right kind of details to point a finger at one factor. Since you don't mention AnyConnect, I am assuming you are running older IPSec/IKEv1 clients.  Two things to look for though:

1.  NAT-T traversal needs to be on.  You should be able to do a "show run | inc traversal".  If you see a result starting with a "no", then just type whatever comes after that "no" into your ASA's config.  It is likely to look like 'no crypto isakmp nat-traversal' (off the top of my head).  It might vary slightly in newer ASA software versions.

2.  You have an ingress ACL on your "inside" or other LAN-security network to prevent certain kinds of Internet access for your users. You can do a "show run access-group" to see what ACLs are applied to which interfaces. If the rules are stringent enough, outbound IPSec/IKE session traffic will be blocked. Looking at the config on the ASA at your other site should guide you there.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jdanaAuthor Commented:
Perfect! Thanks much.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware Firewalls

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.