We have two offices. Two sites connect via IPSEC Tunnel and MPLS for backup. We have an outsource apps server locate at their location. On our WAN-01 router we have a static route to 188.8.131.52 via MPLS ATM link (10.10.10.10). Trace route to 184.108.40.206 stop at 10.10.10.20 (ASA) never pass it. I looked on our WAN-02 and the route to 220.127.116.11 is via IPSEC tunnel. Would this be a problem? From my machine I can access any share or server to the remote location but why my outsource apps doesn't work? This was working fine before we switched to IPSEC Tunnel.
if you want to have also the traffic to/from the server 18.104.22.168 to over the tunnel you need to extend the ACLs that define what has to be encrypted:
for example you could add a second line on the ACL
access-list 100 permit ip siteA.source.net wildcard host 22.214.171.124
and a mirrored line on WAN2 acl
access-list 100 permit ip host 126.96.36.199 siteA.source.net wildcard
if you so this you should be able to carry also this traffic over the IPSEC vpn
Hope to help