Search results for query: *

I have the same problem as yours and getting similar errors: 1 Nov 13 2009 09:53:25 713900 Group = xxx.xxx.xxx.xxx, IP = xxx.xxx.xxx.xxx, construct_ipsec_delete(): No SPI to identify Phase 2 SA! I have updated to 8.2 asa system on all asa, reconfigure asa from the begining and still hav...

and when rebooting with old asa802 image, i get the folowing : Configuration Compatibility Warning: The version 8.2(1)0 configuration may contain syntax that is not backward compatible with the 8.0(2) image that is loaded. *** Output from config line 4, "ASA Version 8.2(1) " . timeout...

I upgrade one more time to asa821, reboot twice, and always getting the folowing error at startup : ..ERROR: IkeReceiverInit, unable to bind to port *** Output from config line 138, "crypto isakmp enable out..." has anyone an idea?

Do You mean after the first reboot with the new asa image? I didnt because I really needed the vpn to be mounted, so I downgrade the image and restart with the asa802...

I have updated the 5505 of the main site with the following command: asdm image disk0:/asdm-621.bin no boot system disk0:/asa802-k8.bin boot system disk0:/asa821-k8.bin But none of the vpn are operationnal anymore, in asdm no interface are enabled for ipsec access. When I try to enable outside...

the problem is much more a directionnal problem, it seems that the vpn tunnel can only open from the main site and not from the remote office. the current work around is a permanent ping from the main site to the remote office, but it is not a solution. i have checked the configuration and the...

I have 3 ASA 5505, on the main site one 5505 is running the asa802-k8 software and at the 2 remote office 2 x 5505 with asa821-k8 software. There are site to site vpn between the offices and the main site and ssl vpn on the main site. everything is running fine until a few days where it becam...