This issue occurs when NATing is not bypassed for outgoing traffic.
Once the Secure Socket Layer (SSL) VPN Client is connected, it shows secured routes. However, the VPN Client cannot ping or access internal servers.
In order to resolve this issue, make sure that NAT 0 and the access-list command for NAT 0 are configured with these commands:
If SSL VPN Clients are unable to access internal sites by name through the ASA, refer SSL VPN clients are unable to access internal sites by name through the adaptive security appliance ( ASA )