Has anyone seen problems when using ver 4.01 of the VPN Client with a PIX? IN several instances we have seen problems where, once connected to the PIX via a VPN, a user can ping a host IP address on the internal LAN, but cannot map a network drive, or perform any "net view" commands.
Disconnecting the VPN and reconnecting seems to fix the problem.
In all cases an NSLOOKUP for the internal host works just fine, and I can ping the Internal host - the problem just seems to be related to accessing shares, etc.
If I add a static entry in the local HOSTS file on the remote VPN PC all works fine. I have seen this occur on both Win2K and XP Pro VPN PC's.
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...