The following example shows sample output for the show crypto engine command when output is specified for a VAC or a VAC+:VAC+:pixfirewall# show crypto interfaceEncryption hardware device : VAC+ (Crypto5823 revision 0x1) VAC:pixfirewall# show crypto ...
I have seen this issue before, and to resolve it I added an access-list to the inside interface to allow allow icmp echo-replies from the internal network to the VPN pool adresses. When I experienced the issue, I checked the firewall logs which were...
From what I see above, it looks like it should work. The only information I haven't been able to verify is on the Branch Office side. Can you provide the NAT info and access-list 110 information from the Branch PIX?
Delete the Static statement and the access for 192.168.2.105 should work. It looks to me like the static statement is overriding your Dynamic NAT. When you only have one public IP address (interface) you should only use the static statement for Por...
