What ports (TCP/UDP) do I need to leave open and redirrect to my web
server on my router to use the WindowsXP RDP protocol (Remote Desktop
Connection). I would like to use both the Remote Desktop Connection
client (communications applet) in accessories -and- the ActiveX
'Remote Desktop Web Connection' (Terminal Services) I have installed
on my home Windows2003 web server.

Both versions work well between computers behind the router. I can
access the web server and even the Web connection service remotely,
but I cannot get a session started (i.e. I cannot access any of my
home computers behind my router). I am using a NetGear MR314 router
which supports both PAT and Port Forwarding.

Thank You;
Michael P Harris
mpharris@usa.net

following states it's tcp port 3389:

http://www.zdnet.com.au/insight/0,39023731,20281706,00.htm

you might also find the following useful:
http://www.microsoft.com/windowsxp/expertzone/columns/northrup/03may16.asp

3389 is the correct port for "straight" Remote Desktop - i.e. using
the Remote Desktop Client program; you can verify this with a simple
NETSTAT at the command prompt - e.g. in the following instance I'm
using my Windows 2003 server as a Remote Desktop client to my laptop:

TCP    WinServer2003Machinename:29391       Laptop:3389      ESTABLISHED

Your ability to remote to your home machine could be limited by your
ISP and/or the firewall at your remote location, even if everything is
configured correctly on your home server and Netgear router.  You
probably won't be able to do a direct Remote Desktop as shown above,
BUT... you might be able to set up your 2003 server using Remote
Desktop Web Connection (served through IIS).

Two basic strategies here:
1) Deploying Remote Desktop for Administration:
   -requires Windows RDP client;
   -Server runs on :3389 by default;
   -Can change listening port from :3389 via registry
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp\PortNumber

2) Use Remote Desktop Web Connection 
   -AutoLoads ActiveX client to client machine via <OBJECT> tag,
    no other client necessary;
   -Get IIS working properly on your server;
   -Set up a test site that's served on an oddball port, e.g. 54934;
   -Set up your router to forward requests from [WAN port 80] to 
    [Server port 54934], using the IP address on which the site 
    in step 2 is configured on your 2003 server;
   -Test that you can successfully view the site internally & externally - 
    from, e.g., a friend's computer - via http://IP_ADDR:54934, where 
    IP_ADDR is your currently assigned dynamic address from your ISP;
   -If step 4 is successful, continue - if not, your ISP is probably blocking 
    inbound requests to client IPs. Use trial and error to attempt to find a 
    WAN port that succeeds - might even work on 80;
   -Once successful, test that you can now do the same from work 
    (or wherever you plan to remote from).  If not, then a company firewall 
    is probably the obstacle;

Once you can get through all the above without problems, then you can
be fairly certain that raw TCP connectivity is be possible.  Then...

   -In server configuration Windows Components, make sure "Web Interface 
    for Remote Administration" is installed and configured (this documentation 
    is in Server 2003 help files). Remote Desktop Web Connection is a 
    subcomponent of IIS/World Wide Web Service in the windows component 
    hierarchy;
   -The default port for this is 8098, 
   -Change the port/IP for IIS in the MMC snap-in for the TSWeb site accoring
    to your succesful configuration details from the previous steps
   -If you change the listening port for this service, you must also edit the
    <OBJECT> tag in the web page to reflect the new port;

If anything here is unclear, let me know and I'll try to get more
complete info from the step things fail at.

Cheers,
Paul

Addendum:

Might have been unclear on one thing on the WIRA [Web Interface for 
Remote Administration] portion.

You need *two* ports that work for the Web Interface configuration - one 
for IIS to serve the page through (default 80), and the other for WIRA to 
listen for a client connection on (default 8098).  If you change the defaults
to e.g. IIS running web on 79 and WIRA on 8099, then you would edit the default
web page in TSWeb so that the <OBJECT> tag lists 8099 as the port, and you 
would browse to URL http://YOUR_DYNAMIC_IP:79 from the remote computer.  

If you cannot send and receive packets between your Windows Server 2003 and
your remote machine on two ports, then you are probably hosed - work firewall,
ISP is blocking, etc.

Hope this helps!

3389 UDP and TCP and you must open also GRE protocol.