Thanks, will try it out around 4pm EST today.
Main Topics
Browse All TopicsI'm currently attempting to replace a Sonicwall TZ150 with a Cisco ASA 5505. With the configuration I've posted, users can get in from outside to the terminal server, but computers can't get out to the internet, nor is the vpn tunnel able to be established.
Here are the paramaters I've been given for the VPN tunnel:
Phase 1:
Authentication: Pre-shared
Encryption: 3DES
Hash: SHA
DH: 1
Lifetime: 86400
Phase 2:
ESP encryption: 3DES
ESP Authentication
Lifetime 28800
The config has been edited to protect my public IP.
Thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Not much experience with the ASA's but shouldn't
nat (inside) 10 access-list cryptomap_acl
instead be:
nat (inside) 0 access-list cryptomap_acl
It would appear that the cryptomap_acl access list is being processed after the "nat (inside) 1 0.0.0.0 0.0.0.0" and therefore the traffic you wish tunneled is instead getting natted? Again - not an expert on the ASA's - just taking a guess....
Lets separate these functions out.
conf t
no access-list cryptomap_acl extended permit ip host 192.168.168.4 object-group remote-vpn-hosts
access-list vpn-policy-nat extended permit ip host 192.168.168.4 object-group remote-vpn-hosts
nat (inside) 10 access-list vpn-policy-nat
no nat (inside) 10 access-list cryptomap_acl
If still not working, have the other end double check their settings. You can also enable some debugging (capture to a text file using Putty or Hyperterminal).
debug cry isa sa 150
debug cry ipsec sa 150
To stop the debug:
undebug all
I do not control the other side, I only have the paramaters that they provided me. Here are the full instructions they gave me:
Our endpoint is: yyy.yy.yyy.108
Our network is: 192.168.50.0 (255.255.255.0)
clinic will need to make ACL from xxx.xx.xxx.4 to host 192.168.50.83 and 192.168.50.86, if portal is used 192.168.50.50
clinic will need to NAT interesting traffic to xxx.xx.xxx.0 255.255.255.0
Phase 1
Authentication: Pre-Shared
Encryption: 3DES
Hash: SHA
DH: 1
Lifetime: 86400 sec
Pre-shared Key: xxxxxxxxxxxxxxxxxxx
Phase2
E
ESP authentication
Lifetime 28800
Thanks,
Dylan
You'll need to get clarification from them if they are expecting an interesting traffic access-list of:
What you have:
access-list cryptomap_acl extended permit ip host xxx.xx.xxx.4 host 192.168.50.50
access-list cryptomap_acl extended permit ip host xxx.xx.xxx.4 host 192.168.50.83
access-list cryptomap_acl extended permit ip host xxx.xx.xxx.4 host 192.168.50.86
Or:
access-lis
With your config, they can't ping xxx.xx.xxx.4. With your config, the 192.168.168.4 host can only initiate traffic to the 192.168.50.x hosts, can you ping 192.168.50.50? If they need to initiate communication to the 192.168.168.4/xxx.xx.xxx.4
They do want to be able to intiate traffic, as they want to test the VPN by pinging xxx.xx.xxx.4. Are you saying that I would need to add a static (inside,outside) statement translating 192.168.168.4 to xxx.xx.xxx.4 and an access-list permitting the 192.168.50.0 hosts to communicate with xxx.xx.xxx.4? If you could provide explicit examples, that'd be great.
Business Accounts
Answer for Membership
by: JFrederick29Posted on 2009-03-27 at 06:51:41ID: 24000825
Add this to get Internet working:
global (outside) 1 interface
For the VPN, post a "show cry isa sa" and a "show crypto ipsec sa" after initiating traffic from the 192.168.168.4 host to a 192.168.50.x host.