Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi Ajavi,The problem is the routing. You have a route pointing to the WAN:route wan 192.168.0.0 255.255.0.0 192.168.201.17 1This means that even the "VPN traffic" goes to WAN interface, thus not reaching the Outside where the crypto map is.Remember t...
The problem here is that you NAT everything, so the traffic reaching the outside interface (post-NAT) does not match your VPN access list:global (Outside) 1 63.174.45.84 netmask 255.255.255.248nat (dmz) 1 172.21.11.0 255.255.255.0In order for this t...
Hi Jacobs,sometime the problem is related to the MTU. There is a "SetMTU" utility in the same folder with the vpn client exec file (i think it is also in the VPN client start menu). Setup the valut 1300 for all connections, reboot and then try the ac...
Hi,The best way is to avoid any overlap between the local LAN and the VPN pool.Try 172.17.0.0/16, is also private IP space:http://en.wikipedia.org/wiki/Private_networkPlease rate if this helped.Regards,Daniel
Yes, you got them all: IP ports 50 and 51 and UDP port 500. Also leave the ICMP ports opened between the IPs for the PathMTU Dicovery.Please rate if this helped.Regards,Daniel
