Win2K TS

Assuming you have a Server, all you have to do is make sure the Terminal Services Component is installed by going to Add/remove programs and then the Windows Components button.  Make sure Terminal Services is checked and ok out.

You will be prompted as to what mode you want to install it in.  If you plan on allowing others, you'll have to use Application Sharing/Server mode.  However, this will require installing Terminal Services Licensing server and obtaining Licenses.  Since you have server at home, I'm guessing your a member of MSDN - a few licenses are included for this with MSDN so you should be ok.

If you just want it for yourself, you can set it up in Administrative mode - this will allows only admins to log in via terminal services.  All other terminal services capabilities are there - it's just a restriction on the class of user.  

Thanks for the information.  Currently it is setup in Administrative Mode and I want to be able to connect from outside of the network.  What does the external client need to use to connect to the network?  I use Remote desktop from within the network.  Not sure about the external client. (Can I create a client termainl service disk to install on the client)

Is the client connection the same if the server was in application mode?

Thanks again for your input.

remote desktop's fine.
connections the same.
If they're win2k clients the terminal services client is usually on the machines in a subdirectory of system32.
just do a search for mstsc.exe and you should be able to find it.

would advise giving it a go and then we'll work through problems if they crop up.
You'll have to know what your IP address is out on your ISP's network too.  
This is usually a dhcp address that gets changed every so often if you're using ADSL or Cable Internet, or a dhcp address that's assigned on connection with a modem.
This address is what the external clients will be connecting to (so if it's a static address it's obviously much easier to get to).

leew, My comment was a clarification of your statement  "this will allows only admins to log in via terminal services.  All other terminal services capabilities are there - it's just a restriction on the class of user."
This is actually on the case where local security policy is left unconfigured.  The difference between the versions is in the number of CALs available by default and what the intended purpose of terminal services is.

Worked great..  Thanks for the help and understanding

Oh yeah.. What about security..  

First of all make sure all your service packs, hotfixes and antivirus definition files are up to date (and kept that way).
Next, have a look at this for ideas on securing terminal services: http://www.windowsecurity.com/articles/Windows_Terminal_Services.html