The SSL VPN Client is unable to access internal servers when split tunneling is enabled on the Cisco ASA

[TCC_2]

Core issue

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.

Resolution

In order to resolve this issue, make sure that NAT 0 and the access-list command for NAT 0 are configured with these commands:

• nat (inside) 0 access-list
• access-list extended permit ( inside network ) 255.255.255.0 (ip pool) 255.255.255.0

Refer to Configure Clientless SSL VPN (WebVPN) on ASA Configuration Example for additional information.

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 )