@mitrushi:
thank you, i will check it out and post back.
Main Topics
Browse All TopicsI have a Cisco ASA 5505 running version 8.2(1)
I'm trying to set it up so to connect using the "Cisco AnyConnect SSL VPN Client"; I am currently using the predeployed Windows version 2.1.0148 of that.
I am able to run that and connect to the ASA remotely. As I watch the logs as a user is connecting, I see no errors. Everything appears to connect successfully, but once the connection process is finished, all traffic on the computer stops. I am not able to ping external or internal IP addresses or otherwise communicate with them.
I'm about 95% sure the problem lies somewhere in the NAT-0 rules or ACLs. I've searched through the forum for quite a while looking for similar cases. I have found a few and have tried comparing my running-config with the ones that are posted and following the changes that are suggested, but I am never able to get a working running-config for myself.
Please take a look at my "show run" output and let me know what I'm missing.
Thank you!
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.
I have modified the config to match that example as closely as possible. The only differences are the obvious instance specific settings (like IP addresses and ranges) etc. Other than that, I think everything else is the same.
The attached log file was started before I ran the SSL VPN "Cisco AnyConnect Client" and was stopped after I disconnected and closed the program.
The noteworthy entries in the logs are things like:
6|Sep 30 2009|16:13:16|106012|10.0.
6|Sep 30 2009|16:13:29|110002|10.0.
3|Sep 30 2009|16:13:38|305005|10.0.
The operational differences between this config and the config in my original post is that, after the VPN completes it's connection process, I am able to access machines on the internet; just not machines on the internal network. Can anybody see what might be missing?
I have gone through your config and I can see that you are missing a nat 0 or no nat entry, unfortunately the Cisco example doesn't deal with this. The idea is that traffic originating from 10.0.0.0/24 towards 10.0.10.0/24 and viceversa must not be translated. So you need a acl and a nat statement
access-list no_nat_vpn_traffic extended permit ip 10.0.0.0 255.255.255.0 10.0.10.0 255.255.255.0
nat (Inside) 0 access-list no_nat_vpn_traffic tcp 0 0 udp 0
Also you have a no crypto isakmp nat-traversal which can cause problems if one of the peers is behind a nat device.
Regarding your log entries the first one is some multicast traffic the firewall is blocking correctly, the second one has to do with Uinversal plug and play which most probably you do not want to allow through your firewall and the third is lack of nat translation from remote vpn which the nat 0 statement will take care of.
OK, I got this working. The combination of the NAT rule and the example from the link from mitrushi is sufficient to make this work. It didn't work for me initially, but I realized I had another problem going against me. It was truly a face-palm moment:
What clued me in was as I was watching the logs on my ASA, I was seeing:
"Built inbound TCP connection 1467 for outside:10.0.10.1/2876 (10.0.10.1/2876) to inside:10.0.0.251/3389 (10.0.0.251/3389) (ssluser1)"
.. and then..
"Teardown TCP connection 1467 for outside:10.0.10.1/2876 to inside:10.0.0.251/3389 duration 0:00:30 bytes 0 SYN Timeout (ssluser1)"
.. but no message saying traffic was being denied or not being able to find a translation group like before.
My ASA is not in production right now, but it is a node on my internal network. All the machines on my network are currently using a default gateway OTHER THAN the ASA. When connection requests were sent, the TCP SYN packets were arriving at the destination host and a TCP ACK packet was sent back to the source. (I discovered this by using Wireshark.) However, because their default route was going to my prodcution NAT/Firewall, they were simply being dropped into the intergalactic bit-bucket.
Thank you, mitrushi, for posting that link. Other examples I had followed didn't even get me close to this solution.
Business Accounts
Answer for Membership
by: mitrushiPosted on 2009-09-30 at 01:55:08ID: 25456630
I don't know if you have come accross this example. /products/ ps6120/ pro ducts_conf iguration_ example091 86a0080975 e83.shtml
http://www.cisco.com/en/US
if it doesn't work we can troubleshoot further