Has anyone ever experienced this wierd issue where once we change the IP of the inside interface of an ASA (5505) we can no longer access it with web based Java ASDM, but regular ASDM client still works ok?
Can't say I have never run into this. Then again I use ASDM for very few purposes. And I always use the software installed on my computer.
Are you saying that with a web browser you cant access the ASA at all?
In some cases where management connections are the problem, removing that management types configurations and re-issuing those commands can do the trick but as you say, you can access the ASA with ASDM.
Or perhaps the issue is that when atleast I use the Web Based Java ASDM it creates a link on the desktop. If you use that link it might use the old interface IP address and doesnt work because of that.
So I found the issue to be with both the ASA and Java. To fix this. The next time you run the wizard on an ASA 5505 and have it's internal IP changed, you will need to go to your PC control panel, Java and delete all the security certificates associated with the old IP. Then reboot *both the ASA and your PC.
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...