>>
>>Nonetheless, to get it to work he'd probably need a static IP (usually an uptick in cost from basic ISP service),
>
>I don't believe this is true using VPN. It is either VPN with computer name, or a static-IP. My source (which does not make the point clear):
>http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx

The client (at work) still needs to be able, somehow, to "find" the host (at home) computer. Fundamentally this means pointing at the IP address of either the VPN server itself, or of a gateway/router that can forward the traffic appropriately. If a Remote Desktop connection doesn't ask for an IP address this is only because the VPN connection itself has been previously configured with the IP address of the desired server (or possibly a dynamic IP or DNS address through a mapping/proxy service).

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.

>
>>All of the above problems are avoided/bypassed by proxy services such as GoToMyPC. If you can handle the monthly or yearly cost it's a pretty compelling solution for casual and/or non-technical users, and worth consideration even for advanced users.
>
>I agree completely. We have a (small) corporate gotomypc account here, and I can easily set different people up when they travel, or whatever, and it doesn't matter what flavor of Windows they have on either end.