topic Problem with cisco vpn client in Network Security

Problem with cisco vpn client

luongdung — Tue, 12 Mar 2019 06:25:18 GMT

We are using cisco vpn client to connect VPN server (ASA 5510).With VPN Connection, Cisco vpn client can only connect the services in LAN other than services is published/NATed to internet via this ASA 5510. For example: On one server, vpn client can not access the services publishing to the Internet while other services not publish to the Internet on the same server remains accessible via vpn client

How can I fix this problem ?

Thanks

Alex

All I can say is you most

Richard Bradfield — Thu, 13 Aug 2015 04:21:37 GMT

All I can say is you most probably need split tunneling on your VPN client so access to public addresses does not go through the VPN tunnel.Also you might need to manipulate your DNS

Hi Alex, I would agree with

rizwanr74 — Thu, 13 Aug 2015 14:37:57 GMT

Hi Alex,

I would agree with chrbradf1, if you have a given publically accessiable services running on a server, then you must include that paticular public ip-address in the split-tunnel acl and you don't include that IP-address for nat-examption that should work for you.

thanks

Rizwan Rafeek.

Thanks rizwanr74 and

luongdung — Fri, 14 Aug 2015 06:14:23 GMT

Thanks rizwanr74 and chrbradf1. Vpn client can connect the service with the public ip address on the server but can not access the same service with local ip on the same server

How can I fix this problem ?

Alex

Hi there, "Vpn client can

rizwanr74 — Fri, 14 Aug 2015 15:46:07 GMT

Hi there,

"Vpn client can connect the service with the public ip address on the server but can not access the same service with local ip on the same server"

Reason that client can access service on public address either because they are accessing it outside of the tunnel or via the tunnel by the means of split-tunnel.

The reason why cannot access it on private address, is because the static-nat public to private. The return traffic will be subject to static-nat which will resulted in asymmetric traffic path.

Your client cannot access static-natted private address, unless they are access it on public address, the reason asymmetric traffic path.

Hop that helps.

thanks

I think this will be a DNS

Richard Bradfield — Sat, 15 Aug 2015 23:47:51 GMT

I think this will be a DNS issue, You will need to have a DNS server that the VPN clients use that points to the internal address of public facing servers