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

[Yury Kolos]

Thank you all, guys!
I sure the trouble in Remote Desktop App. I use Shrew or Cisco VPN many
years without troubles. This issue is the first one.
I've sent message to developers.


--
Best regards, Yury

2018-06-18 13:40 GMT+03:00 Seth Dunn <seth at d2ms.com>:

> Couple things I would check since this is RDP, and you say that connecting
> to other things works fine…
> Windows Firewall on the target box
> The target box can accept RDP connection (Control Panel\System and
> Security\System\Remote Settings)
> If it can, then I would remove the check mark from the box for Allow only
> computers running NLA
>
> I assume you are able to ping the target box?
>
>
>
> *From:* vpn-help [mailto:vpn-help-bounces at lists.shrew.net] *On Behalf Of *Yury
> Kolos
> *Sent:* Monday, June 18, 2018 4:01 AM
> *To:* Larry Moore <lmoore at starwon.com.au>
> *Cc:* vpn-help at lists.shrew.net
> *Subject:* Re: [vpn-help] Win10 RemoteDesktop App cannot connect through
> ShrewVPN
>
>
>
> Hello Larry,
>
>
>
> 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
>
>
>
> Yes, you are right. 192.168.71.3  it's LAN IP of my PC. 172.17.19.0/24 -
> it's VPN-subnet.
>
> I don't understand why traffic not going through VPN subnet when I use
> RemoteDesktop App, but does so in any other application including
> RDP-client.
>
> Thank you very much for your help. I've understood the problem in
> RemoteDesktopApp.
>
>
>
>
>
>
> --
> Best regards, Yury
>
>
>
> 2018-06-18 2:19 GMT+03:00 Larry Moore <lmoore at starwon.com.au>:
>
> 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    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     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.
>
>
> _______________________________________________
> vpn-help mailing list
> vpn-help at lists.shrew.net
> https://lists.shrew.net/mailman/listinfo/vpn-help
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20180618/64afd9c4/attachment-0001.html>