You're welcome. The primary setting is to enable the interface to listen for incoming remote access VPN connections: webvpn enable outside (assuming "outside" is the nameif of your primary ISP interface - otherwise substitute the actual nameif) In ASDM that's what happens when you check the box in the remote access VPN connection profile to enable the VPN on the interface and apply the change. In addition to that, for a full setup, you should have a public DNS entry that maps that interface IP Address to an FQDN and a certificate installed that has that FQDN as a Common Name (CN). ... View more

" By the way i do have 2 ISPs connected to my firewall, would that also cause the problem? How to dedicate my SSL VPN into a single ISP? " This may be part of your problem. ASAs don't typically handle dual ISPs well for incoming traffic since they only have a single default route outbound. The traffic comes into ASA based on address where you are hosting the VPN page. If it is all setup on the VPN configuration, the ASA will reply to the client using the interface that is appropriate for the default route (i.e. your primary ISP). So the tcp 3-way handshake will never succeed. One can use a second ISP for failover (route tracking and IP SLA etc.) or with policy-based routing (PBR) if you want to direct traffic to some known destinations down the second ISP. However if you have remote clients at random locations on the Internet you will always use the default route to reach them from the ASA, even if they arrive via the second ISP. ... View more

Your access lists are permitting all IP traffic so they are not really restricting anything (except non-IP like icmp etc.). Your NAT rules will make any server in the DMZ appear to be the interface address. Is that your intention? ... View more