Behavior of vpn client connecting to ASA site to site connection
I have connected a remote office using an ASA 5505 to the main office which uses NSA 3500 Sonic Firewall. I was able to bring up the site-to-site vpn and can ping clients on each end. I was also looking at configuring vpn client access for employees who travel. The remote office behind the ASA has a backup domain controller to store the profiles but the exchange server is at the main office behind the Sonic Firewall. If I connect a VPN client to the ASA (remote office); the employees can pull their profile; however, they can't access the exchange server. If they connect to the Sonic Firewall then they can't pull their profiles. People at the main office and remote office have no problem accessing resources.
VPN Client (on the road) --> ASA 5505 (remote office) --> (site-to-site connection)--> Sonic Firewall (main office) --> exchange server
I can ping vpn client to ASA. I can't ping the exchange server. People at the remote office can access everything at the main office and vice versa.
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...