<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Yury,<br>
      <br>
      On 17/06/2018 5:08 PM, Yury Kolos wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAEdtFYNiHxucpCNOTfvF7TixE7-vWXP7WbtsMw5E_HN4A_64DQ@mail.gmail.com">
      <div dir="ltr">
        <div>Thank you for your response Larry.</div>
        <div><br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div> It would seem your VPN tunnel is working just not the
            application. <br>
          </div>
        </blockquote>
        <div>App not working only through ShrewVPN.</div>
        <div><br>
        </div>
        <div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"> I expect you will see
            some packets relating to connection establishment. If so,
            could your PIX be performing deep packet inspection and
            blocking the connection!?<span class="gmail-HOEnZb"></span><br>
            <span class="gmail-HOEnZb"></span></blockquote>
        </div>
        <div><br>
        </div>
        <div>When I connectin RDP-client I see established connection in
          netstat utility:</div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>netstat -na | findstr 111.250<br>
            TCP    <a href="http://172.17.19.150:49942"
              moz-do-not-send="true">172.17.19.150:49942</a>    <a
              href="http://192.168.111.250:3389" moz-do-not-send="true">192.168.111.250:3389</a>  
            ESTABLISHED<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <br>
        <div>But when I try to use Remote Desktop App I see only
          Syn_Sent in netstat:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>netstat -na | findstr 111.250<br>
            TCP    <a href="http://192.168.71.3:49929"
              moz-do-not-send="true">192.168.71.3:49929</a>     <a
              href="http://192.168.111.250:3389" moz-do-not-send="true">192.168.111.250:3389</a>  
            SYN_SENT</div>
        </blockquote>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    Note the source IP of 192.168.71.3 above. I am assuming this is the
    IP address of your LAN and I suspect is where your problem begins.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAEdtFYNiHxucpCNOTfvF7TixE7-vWXP7WbtsMw5E_HN4A_64DQ@mail.gmail.com">
      <div dir="ltr"><br>
        <div> Packet trace in attachment. Could you see?<br>
        </div>
      </div>
      <div class="gmail_extra"><br>
      </div>
    </blockquote>
    <br>
    Looking at your packet capture I can see three RDP sessions going
    through the Shrew VPN, I am also assuming these connections were
    made after the above 'netstat' command was issued.<br>
    <br>
    I expect if you perform a packet capture at the gateway for the
    subnet 192.168.71.0/24 and you look for packets destined for host
    192.168.111.250, you will see the SYN requests arrive. If so, you
    will need to determine why your Remote Desktop App is using your
    LAN's default Gateway instead of the routes set up by Shrew VPN.<br>
    <br>
    Regards,<br>
    <br>
    Larry.<br>
  </body>
</html>