[vpn-help] Win10 RemoteDesktop App cannot connect through ShrewVPN

[Larry Moore]

Hi Yury,

On 17/06/2018 5:08 PM, Yury Kolos wrote:
> Thank you for your response Larry.
>
>     It would seem your VPN tunnel is working just not the application.
>
> App not working only through ShrewVPN.
>
>     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!?
>
>
> When I connectin RDP-client I see established connection in netstat 
> utility:
>
>     netstat -na | findstr 111.250
>     TCP 172.17.19.150:49942 <http://172.17.19.150:49942>
>     192.168.111.250:3389 <http://192.168.111.250:3389> ESTABLISHED
>
>
>
> But when I try to use Remote Desktop App I see only Syn_Sent in netstat:
>
>     netstat -na | findstr 111.250
>     TCP 192.168.71.3:49929 <http://192.168.71.3:49929>
>     192.168.111.250:3389 <http://192.168.111.250:3389> SYN_SENT
>
>

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.

>
> Packet trace in attachment. Could you see?
>

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.

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.

Regards,

Larry.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20180618/537215da/attachment.html>