Thanks for the reply, but unless I'm missing something the thread you linked and others with similar titles all pretty much lead back to the same conclusion that something is wrong with how the routing is handled when IPsec is invovled.
This leaves me in the same position of wondering how I can troubleshoot this problem and/or work around it. I tried editing the route 220 table, but this didn't change the outcome
