Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • I currently already do everything you mention. Forward ports on my router (btw 80 is not required for RDP that I know of, am I missing something?), also use DynDns (my provider says they do dynamic IPs, but it hasn't changed in a year, but still...). The problem is once the machine is on the VPN it ignores any traffic coming through the actual internet and everything is routed from the remote gateway (at least how I understand it). The exception is when I'm on the local network, local ips are routed appropriately. Commented Oct 18, 2010 at 19:21
  • Also, from my experience "If you are able to determine the public ip address of the host pc and that ip address doesn't change then you can connect via that address, whether or not you are connected to a VPN or not." is not correct. If I'm connected via the domain name or the ip, an initiate a VPN, the RDP connection is lost. Commented Oct 18, 2010 at 19:22
  • Whenever you initiate or disconect a VPN then you are in essence disconnecting from the internet for a brief period of time. This is unavoidable. It's the same as if you disconnected the cat-5 cable, or switching wireless access points. Commented Oct 18, 2010 at 21:16
  • Can you provide some documentation on what you're saying? Commented Oct 22, 2010 at 20:00
  • Wouldn't the easy solution be to have a second NIC on the machine, and have the router forward port 3389 to that port? I have done that in the past with my server, with one WAN facing NIC and one for LAN and RDP.
    – paradroid
    Commented Nov 26, 2010 at 12:42