W2K Terminal Server

First you have to enalbe Terminal Server (TS) on your W2K server.
Next you will have to use Terminal Server client to connect to it. Since TS Client works via the network it is possible to connect to your Server by using the IP address. In the Server address box enter the IP address. If you use a firewall you will have to open TCP port 3389.
TS has 2 modes; 1) Application Mode, 2) Remote administration mode. you configure this in the terminal server configuration MMC Snap In, or when you install terminal server. Application mode requires a TS License Server (after 90 days of use, the License Server has to be a Domain Controller in a windows 2000 domain, in a WINNT domain it has to be a windows 2000 server), Remote Administration Mode desn't require one. If you use application mode you can use it as a remote adminsitration mode also, but it uses a license. In Remote Administration Mode, only 2 people can be logged on at once.
You can use Terminal Server Advanced Client (TASC) which is available for download at microsft's web site. TSAC allows you to use a web browser to connect to your terminal server (the first time you use it, the browser downloads an ActiveX control). The TSAC doesn't have to be installed on the same computer as the TS, it can be installed on any windows machine that runs IIS.
To configure it with security you can just make sure that a user name and password is required for that resource on that web site.
Once you get to your TS web page (from your browser) you just enter the IP address in the server box and you click connect. The browser (not the server) then makes a direct connection to the TS from the clients browser using the ActiveX control.

First you have to enalbe Terminal Server (TS) on your W2K server.
Next you will have to use Terminal Server client to connect to it. Since TS Client works via the network it is possible to connect to your Server by using the IP address. In the Server address box enter the IP address. If you use a firewall you will have to open TCP port 3389.
TS has 2 modes; 1) Application Mode, 2) Remote administration mode. you configure this in the terminal server configuration MMC Snap In, or when you install terminal server. Application mode requires a TS License Server (after 90 days of use, the License Server has to be a Domain Controller in a windows 2000 domain, in a WINNT domain it has to be a windows 2000 server), Remote Administration Mode desn't require one. If you use application mode you can use it as a remote adminsitration mode also, but it uses a license. In Remote Administration Mode, only 2 people can be logged on at once.
You can use Terminal Server Advanced Client (TASC) which is available for download at microsft's web site. TSAC allows you to use a web browser to connect to your terminal server (the first time you use it, the browser downloads an ActiveX control). The TSAC doesn't have to be installed on the same computer as the TS, it can be installed on any windows machine that runs IIS.
To configure it with security you can just make sure that a user name and password is required for that resource on that web site.
Once you get to your TS web page (from your browser) you just enter the IP address in the server box and you click connect. The browser (not the server) then makes a direct connection to the TS from the clients browser using the ActiveX control.

James,
This helped me get going with terminal services:

http://www.dslwebserver.com/main/fr_index.html?/main/sbs-Terminal-Services-Server-Configuration.html

I recommend using IIS and the TSAC(web client) you don't have to worry about loading a client on PCs where you want to remote from. However you can choose not to install the TS Web Client on the server and load the TS client program on whichever machine you want to access the server from (if you are concerned with security). However I will note that by default the permissions allowed for the "Remote Administration" flavor of TS is set to allow administrators only. Look under AdminTools -- Terminal Services Configuration. Properties of the RDP-Tcp connection, then permissionstab. I would recommend installing the latest security hotfixes from Microsoft too, if you want to use the Web Client. I have been using it for a while and I have no worries. Hope this gets you started. Good Luck!

Answer #1 is exactly on the money! on last comment is that you can use the traditional Terminal server client installed on a remote system.

I find the web client to be excellent, but the desktop client is slightly simpler because a single icon will open the session, however a detailed URL shortcut can do the same thing.
Example:
http://wts.yourdomain.com/connect.asp?Server=wtsserver.yourdomain.com&rW=800&rH=600&