But I can ping my router ip via cmd, so coming from outside can be done through my router I should be able to reach inside my home Of course the remote computer is not on the network I'm on right now it's on my home network. >But this not true, as I just left home 30 mins and it's rarely off, only rebooted sometimes.ģ) The remote computer is not available on the network. >But this is not true, as I am able to RDC at home to the server machine. DONE, I THINK, BY ENTERING :3389.īut the message result is always the typical:ġ) Remote access to the server is not enabled. Open Remote Desktop Connection and connect. DONE - Using 'what is my ip' ,easy enough.
But in desperation I may try disconnecting it and heading out again to the local Starbucks to try connecting.įind your router's public IP address so that Remote Desktop can find it on the Internet. House, is this a problem requiring additional config? I don't believe it has an ip address or acts like a router. Note: Using a wifi signal booster in the far end of the DONE - NOT TCP/UDP but only TCP, internal and external port ranges the same. Open your router's configuration screen and forward TCP port 3389 to the destination computer's IP address. Make sure Remote Desktop is able to communicate through your firewall. DONE - FOR BOTH PUBLIC AND PRIVATE ASPECTS OF THE RULE.įind the IP address of the computer on your home network that you want to connect to. Connecting from Win 7 so this authentication method shouldn't be an issue, I
DONE - ADDED ROLE TO SERVER AND NON-ADMIN ACCOUNT TO RDP GROUP, using Network Level Authentication. Allow remote connections to the computer you want to access.