Unless you have nat configured going from your inside to your outside interface, the pool IP addresses should be able to access the internal network without NAT. Their next hop is the firewall, and if the firewall knows how to route to the rest of the network, you are fine.
If you do have a nat0 - you will want to put a statement in your nat0 access-list (or create one) saying anything going to the pool addresses doesn't need to be translated.
The only caveat is that the rest of your network needds to know where the pool resides - when a packet gets to those internal devices, do they know how to route the source address back to the ASA? That catches a lot of people
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...