How does Anyconnect VPN Client change/affect local windows routing table?
I have this problem:
Before connecting with Cisco Anyconnect VPN, the "route print" command on Windows XP doesn't show any special static route entry.
After connecting with Anyconnect, I can see a static route pointing to my DHCP & Novell Server (internal network interface, nothing to do with VPN). That means, that after being connected, I cannot access this server anymore, as packets are routed directly on the internal network.
This way, I have like an unwanted "Split Tunnel" situation, even though in ASA Config, in the group policy, I say to "tunnel all networks".
When I try to manually remove the static windows route, the process "vpnagent" recreates it directly afterwards.
Does anyone know how the route table modification process of Cisco Anyconnect works?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...