Over the past week we have been migrating remote offices to a new 3005. Because of routing, we had to assign new IP addresses to our 3002s.
We've had a couple of job sites that were migrated that connected, but they were unable to reach 95% of internal resources. They were able to get to the network, authenticate (partially), and go out through our Web proxy.
I've done tracerts and clients at the remote offices can reach, ping, resolve names just fine, but for whatever reason applications won't open, email clients won't connect, etc.
One location had a linksys router infront of the 3002. We removed that, and that location failed to have any further problems. However, another location where the 3002 is plugged in directly to a dsl modem, the problem continues. We had to re-direct its connection back to the old location. We have 10 that work on the new location, and this one that is still a problem.
Any thoughts about what could be going on?
We change the configuration by downloading the config.txt file, modifying it and importing it back into the 3002.
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...