Windows 10: RDP Access to A Client PC from Outside LAN Environment

Hello there, I realize that this query has been brought up a number of times, yet I am having difficulty connecting to a client machine from outside my LAN. Both Machines are Windows 10 Pro, LAN environment is Windows Domain. I am connecting using a random port number XXXX in lieu of the actual RDP port number and using port translation on my firewall to direct the traffic to the specific machine over port 3389. I have successfully used this configuration with other Windows 10 Pro PC's in my domain, however I now have a PC which I am unable to connect to from an external network, yet the RDP c

:)

 

Can't setup new VPN connection for outside RDP access.

I found it. Please disregard my previous reply. Kindly review the attached screen shots.

 

Guidance needed to setup my Home PC access over Internet through browser

I wasn't giving steps on how to get RDP working, that is covered plenty of other places, I just give the steps to make it secure.

RDP. If they aren't tracking your Web browsing, I doubt they are going to track RDP.

And if you start the session from the command prompt it doesn't even put the address in the MRU list.

Though the question that needs to be asked now is, what are you using for your VM lab?

 

Guidance needed to setup my Home PC access over Internet through browser

Yes but to do a remote access outside the network he'd likely have to forward port 3389 (or whatever port he chose if standard RDP port was in use or he wanted to play it safe-ish) to that PC in order to connect over WAN. RDP's great locally, especially if you know users won't be logged in when you're trying to use basic RDP. But over WAN, I'd rather do something with a little more security and through an encrypted tunnel or connection if possible. That's why I suggesting Teamviewer, OpenVPN or RDGateway to manage that connection when you throw navigating over public networks to reach said LAN into the mix.

Maybe I misread what he's trying to do or maybe I'm reading too much into it. *Smile

If it were me wanting to connect to my network, I'd do what I am now... OpenVPN tunnel with credentials to even connect in the first place, with a Teamviewer fallback. But my method works for me, might not work as well for others.

Any reason you prefer Tunnelblick over the OpenVPN client on Windows? Last I checked Tunnelblick was for OSX??? I've used it with success in that environment. I gotta say the OVPN client for Windows has been rock solid in my experience, right now I have about 10 different OVPN networks I connect to at any given time and it's painless and easy.

Just remember to run the OVPN client as admin in Windows or with SU elevated permissions in Linux and I believe the same in OSX. If you don't run the OVPN as admin in Windows, you'll connect but your routes won't work because your routing table will not be modified...so you will never actually be able to reach the subnet on the other end.