On 17/06/2018 7:13 AM, Yury Kolos wrote:
Hello, Peter
I know that 192.168.111.250 is LAN IP of my remote server (in office
network). I use ShrewVPN from my home.
I have a lot of RDP servers and I don't want to port forward they all.
That why I need VPN solution.
I guess you had not understood this issue.
See below:
"ShewVPN" + "Remote Desktop App" + "LAN IP of remote RDP-server" =
*ISSUE* (cannot connect).
"ShewVPN" + "RDP-client (mstsc)" + "LAN IP of remote RDP-server" =
*OK*.
"Remote Desktop App" + "WAN IP of remote RDP-server" = *OK*.
"RDP-client (mstsc)" + "WAN IP of remote RDP-server" = *OK*.
Classic RDP client (mstsc) and Remote Desktop app use the same TCP
port 3389.
When I try Remote Desktop App through ShrewVPN I don't see any
attempts on my Cisco PIX debug logs. Classic RDP client does
footstep//s in Cisco logs.
I hope you can make conclusion from information above issue in
ShrewVPN software.
Debug logs: https://blancos.info/debug.zip
<https://blancos.info/debug.zip>
Thank you for your response!
It would seem your VPN tunnel is working just not the application.
In Shrew VPN Debug Options, you could simply enable only "Enable packet
dump of private interface traffic" with a tick, restart the Shrew IPSEC
Service then re-establish your VPN tunnel.
Using MSTSC connect to the RDP server then logging off.
Using the RemoteDesktop App, attempt a connection. When the timeout
occurs, remove the tick from "Enable packet dump of private interface
traffic" and restart the IPSEC service.
Examine the packet capture file looking for the connection using the
RemoteDesktop App, 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!?
Larry.
_______________________________________________
vpn-help mailing list
[email protected]
https://lists.shrew.net/mailman/listinfo/vpn-help
