LAN to LAN VPN between ASA 5505 to PIX 506 stopped working after IP address change
A client has an ASA5505 in the office and a PIX 506 at home. This was set up with a Lan to Lan VPN. The PIX outside interface is set for DHCP and the address hasn't changed in 3 years until a couple of days ago. I changed the endpoint (peer) address on the ASA to match the new IP from the PIX, but still no connectivity. A packet trace on the ASA goes through route inspection, nat, etc. just fine then ends at the VPN with the following:
"Type-VPN, Subtype-encrypt, Action-DROP"
Any thoughts on what else I might have to do to get this working again?
The client has made NO CHANGES to the PIX and the only change I've made to the ASA is to set the PEER to match the new address.
I also noticed that the name of the tunnel-group is the old IP address - that shouldn't matter should it? I can't change it through the GUI, but when viewing the running config, it shows as such:
tunnel-group 24.x.x.x type ipsec-l2l
tunnel-group 24.x.x.x ipsec-attributes
pre-shared-key *
The actual address is now 98.x.x.x
"Type-VPN, Subtype-encrypt, Action-DROP"
Any thoughts on what else I might have to do to get this working again?
The client has made NO CHANGES to the PIX and the only change I've made to the ASA is to set the PEER to match the new address.
I also noticed that the name of the tunnel-group is the old IP address - that shouldn't matter should it? I can't change it through the GUI, but when viewing the running config, it shows as such:
tunnel-group 24.x.x.x type ipsec-l2l
tunnel-group 24.x.x.x ipsec-attributes
pre-shared-key *
The actual address is now 98.x.x.x
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER