Hi Fred:

Without spending any more money you may not be able to make this work, at
least not legally.

As I remember the terms of Server 2000, a Desktop 2000 was granted a TS
license.  I may be mistaken, and there is a chance that the license extends
to XP.

For TS to anything, you have to open the appropriate ports on your router
and forward them to the ip address of your server.

The router must pass GRE 47, and you have to open and forward 1723.

For MS networks, you then use the Add a Network Connection Wiz to add the
VPN connection to "The Network at My Workplace" and feed it the ip numbers
of your public facing device, typically the router/firewall.

For Hardware capable VPNs you may need an identical device on each end, or
you may need some piece of software that installs on the remote computer
that creates the tunnel.  Check with your mfg.

Once the VPN connection is made, you use RDP to connect to the ip address of
the server.  This works because the VPN connection is issued an IP in the
correct range for the VPN to be in the same network as the server.  You find
that little gem in Start - Programs -  Accessories - Communications.

One rule is that the remote and the office use different subnets, so if the
office was on 192.168.16.X, the home systems internal side has to be
anything else.

You can't use the W2K3 server, as it requires the installation of TS
licenses, ($90 ea and would require spending money) which were granted by
W2K as a part of the package.  Although truthfully this is the way to go, a
second box for TS.

Lastly, you need really strong pass phrases if you are going to do this.  My
C@t has 10K flea$ is a pretty good one.  Can't be forgotten, and a zombie is
not going to hit it.