I have an issue and was wondering if anyone had similar problems and what was done to resolve it.
The basics: upgrading from 4.5.1r654 to 5.0r176 for ~28K hosts. Schedule the software upgrade, user gets it when on the network, goes home connects to home network and can't get to internet/vpn or anywhere. They come back to work, boot on the network and are fine.
Sending out the software update with a required reboot is not an option (politically speaking).
Correct, we're not forcing a reboot after the upgrade.
We're still testing whether it works when they go home again. It doesn't matter if they are in testmode or not, it seems they cannot get an IP address either way on their home network. The MC is only reachable from the corporate network except thru vpn. They can't vpn in because they aren't getting an IP.
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...