For your port numbers and setup take a look here :^)

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20580074.html?query=RDP++port+number&searchType=topic

I see port 80 and port 3389...After reading that article I'm not sure which??  please help.

3389 in concerned with RDP = Remote Desktop Protocol

Where as Port 80 is standard http (Web Traffic)

You can change the port number for RDP (but this has security implications :( ie do you want a remote desktop session open on port 80 on your home or corporate PC)

If you want to change the port number

*****
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You can use the Remote Desktop feature in Windows XP Professional to connect to your computer from another, remote computer. WARNING: The Remote Assistance feature in Windows XP may not work properly if you change the listening port. To change the port that Remote Desktop listens on:
Start Registry Editor (Regedt32.exe).
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

On the Edit menu, click Modify, click Decimal, type the new port number, and then click OK.
Quit Registry Editor.
NOTE: When you try to connect to this computer by using the Remote Desktop connection, you must type the new port.
Keywords: kbhowto kbnetwork KB306759
Technology: kbrdcMac100 kbrdcsearch kbrdcWin100 kbWinXPPro kbWinXPPro64bit kbWinXPProSearch kbWinXPSearch kbZNotKeyword

*****


Port 80 was ONLT stated in the Q above because the user wanted to connect via his/her IIS homepage

So the answer is PORT 3389 is the one you want opening :^)

Pete

:0) ThanQ

I am a home user of Remote Desktop. It's not working since I rebuilt XP.
Do I need settings under TCP/IP Advanced Port settings to be added?

I open port 500, both ways on my router. This allows rdp fine. Not too sure about port 3389 - never come across it when enabling rdp across the internet.

Hope this helps.

Port 3389 is the proper port for remote desktop.

Please be advised that most people who leave the built in firewall turned off will need to allow Remote Desktop within their firewall if you should enable the firewall during the SP2 install.

Changing the ports becomes critical if you have several RDP enabled boxes behind a firewall and you only have a single IP address to play with. I have 3 machines behind a firewall that I wanted to access via RDP had to change the reg settings for two of the three and forward those ports in the firewall. All worked great until I tried to PCAnywhere into one of them after initiating a terminal serices session. Seems they don't get along with each other and once you have remotely connected via RDP and then attempt to connect via PCAnywhere all you get is a black screen and blinking cursor on the remote. Tried to alleviate this issue without success. Had to stop the PCAnywhere host and restart the host to enable proper PCAnywhere functionality. Weird problem but not unknown as i found mention of it on Symantec and Google.

albiemanmike, why don't you use Remote Desktop Web connection. It seems to me it will solve all your problems. Just give different port numbers to different machines and open the port in your router.

RDP port 3389

If I have three machines configured to listen on three different port numbers, how would I remote into one of them? What would that look like? Something like this?

123.23.123.44:3389

Would that be correct?

Thanks

Dave

yes 123.23.123.44:3389

"Changing the ports becomes critical if you have several RDP enabled boxes behind a firewall and you only have a single IP address to play with."  I assume that you are creating a service through the firewall using the IP address and port number. The result is lots of individual services opening up the firewall to the customized port numbers (one for each rdp box behind the FW.) A better and more secure approach is vpn connection authenticated through the firewall per user with the user than making rdp connection via their LAN IP address. My users like their firewall holes because they don't have to futz with VPN, but I don't like the idea of port bangers getting through the firewall without authentication to hack at the individual machine linked through the service. Even with DHCP, local addressing is pretty stable and if it is really an issue your remote access users can be assigned static ips for their individual machines. You can still change port numbers if you want to and that might slow down someone who cracks through authenticated VPN, figures out local ip address, user name and rdp password. We use  PPTP for our individual vpns although we could use ipsec if you are looking for even more secure connection. Depending on the firewall, there are also proprietary client vpn  solutions (essentially forms of ipsec) with ease of use advantages. Last but not least, always worship at the church of strong passwords. This is the ultimate and last ditch defense at the gate.

PeteLong is correct. Port 3389 is default port number for Remote Desktop.