>>
>>The link you supplied shows configuration and operation of Remote Desktop assuming the VPN has already been established. It's the establishment of the VPN connection that (ultimately) needs the IP address of the server computer.
>>
>
>The host can be behind a firewall. The host does not have to have a static (as in public, ISP provided) address. A firewall can take care VPN routing. My only point is that you do not have to have the additional expense of a static IP to (safely) use Remote Desktop.

While a firewall can handle VPN routing, the client still needs to know how to reach that firewall - IOW it has to know the firewall's public IP address. If IP address of the server side/firewall (i.e. his home) changes, the VPN will break until the client is reconfigured to make use of the server's new IP address. Some ISPs change their client's IP address frequently (I believe up to several times per day in some cases), others not for several months at a time (i.e. "pseudo-static"). The most convenient way to avoid this problem is to make sure the server side IP never changes - i.e. pay extra for a static IP address.

Dynamic DNS/IP services can save the generally extra cost of a static IP at the price of some more complexity.

>
>But it is a moot point; Jay most likely does not own a firewall that is up to the task. Both of our final recommendations are the same.

Agreed!