Well, there's no way around that with DHCP enabled. If you want your computer to accept it's IP through DHCP configuration, you'll have to accept that it's possible that your computer might reboot for some reason sometime while you're not there and get a new IP, and then your NAT settings in your router for Remote Desktop won't work. Well they'll work, but they'll point to an IP that is either not associated with a computer, or is associated with a computer other than the one that has RD set up.
Here's what I did:
1) Told my router to only give out IP addresses 192.168.2.4 - 192.168.2.40 through DHCP.
2) Told my router to forward requests directed at port 3389 to IP address 192.168.2.3.
3) Configured the TCP/IP protocol settings on my PC for static IP (disabled automatically getting it via DHCP):
3a) Set my IP to 192.168.2.3.
3b) Set both gateway and DNS to 192.168.2.1.
This prevents the router from assigning the IP via DHCP that I configured in the port forwarding/virtual server part for my PC (192.168.2.3), yet still allows other PCs and devices to obtain their IPs via DHCP.
You'll also need to allow remote desktop connections.
1) PC software firewall
1a) Windows firewall - If on, make sure there is an exception enabled for Remote Desktop
1b) 3rd party - Allow connections on port 3389
2) You need to add which user account(s) you want to connect to remotely to the Remote Desktop Users group. (or maybe it's just Remote Users).
3) The account(s) that you want to be able to connect to must have a password enabled. I HIGHLY recommend a very strong password, including random characters in random places, numbers, symbols, caps and lowercase.
4) Remote Desktop needs to be enabled. You get to this by the System applet (in Control Panel or by right clicking My Computer | Properties), Remote tab.
If you don't want to allow remote login access for users in the Administrators group (including the Administrator account itself), you need to change a setting in the local policies MMC snap-in. Administrators by default are allowed to connect even if they aren't in the Remote Desktop Users group. I'll look up the specific location of this setting later when I get a chance.
To connect remotely, you just type your external IP in the Remote Desktop client and hit connect. A request is automatically sent to that IP on port 3389. The router receives it and sees that it should send requests coming in on this port to the configured IP (in my case 192.168.2.3). The RD host computer recieves the request, assuming an exception is enabled on the host PC's software firewall, and assuming RD is enabled, ititiates the RD session by asking for the account log-in information. Then you just type in the username and password for the account you want to connect to. If this account is in the RD Users group or the Administrators group (default behavior), then it will log you in, and it is basically as if you are sitting there at the computer, albeit slower.
Sorry if it sounds dumbed down or obvious to you. I don't know your specific level of knowledge, so don't take it as a personal insult. I just want to be as helpful as possible.
Facebook
Twitter