I have a VPN 3005 concentrator in a Windows environment. The private interface is in one locations, and the 3 remote sites are on a private WAN. I can ping, and using an IP address, terminal services and other service work fine. Name resolution is prived via DNS (Windows AD). I can ping by name any host on the subnet attached directly to the private interface, but names are NOT resolved to the other remote subnets. Since I can ping from a VPN client, I don't believe I have a routing issue. I can also manually add the DNS server IP addresses to the Windows Local Area Connection created by the VPN client after the connection is made. The concentrator has the DNS entries, and the DHCP assignment is provided a Windows server. The clients are running Win XP and version 4.7 of the Cisco VPN client, the 3005 is running version 4.
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...