Link to home
Start Free TrialLog in
Avatar of js23847
js23847

asked on

Windows XP Remote Desktop PORT???

I'm looking for the port # for the built in "Remote Desktop" feature of Windows XP -- I need this port to enable port fowarding on my router so I can get in remotely...thanks!
Avatar of Pete Long
Pete Long
Flag of United Kingdom of Great Britain and Northern Ireland image

Avatar of js23847
js23847

ASKER

I see port 80 and port 3389...After reading that article I'm not sure which??  please help.
ASKER CERTIFIED SOLUTION
Avatar of Pete Long
Pete Long
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
: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.
if you're interested in configuring your network/pc so that you can Remote Desktop your PC from an external network, you need to do 2 things:

- configure your PC with a static IP address
- setup a port forwarding rule on your router to forward port 3389 (RDP) to the static IP address of your PC

You can setup a static IP address on your PC by:

Right clicking on My Network Places
Right click on whatever connection you use to connect to your network (Local Area Connection or Wireless), and click Properties
Double click on Internet Protocol (TCP/IP)
Select "Use the following..." for both IP address and DNS servers

You will want to give your PC an IP address on your network that's in the same subnet and isn't being used.  Here is a good write up on the differences between Static and Dynamic IP addresses and how to configure each: http://portforward.com/networking/static-xp.htm

Then you will want to configure your router with a "port forwarding" rule, passing port 3389 (the port that RDP runs on, by default) to the IP address of your PC, which should now be static.  

Now for all of this to work, you need to know your public IP address (the IP address given to you by your ISP - verizon, comcast, etc.), which you can get by visiting www.whatismyip.com.  You can use this IP address from a RDP enabled PC on a separate network to access your PC at home, by going to Start > Run and type in mstsc in the run box to bring up the Remote Desktop Connection box.  Type in your Public IP address and click enter, so long as you have all of the other criteria for allowing your PC to be RDP'd, then it should work.  However, the majority of home networks have dynamic IP address given to them by their ISP - when your public IP address changes, you need to know what the new address is so that you can access your PC from an external network, the old IP address will no longer work.  A better practice would be to setup a dynamic dns address, so that your public IP address will be accessible by a name, such as bobspc.homeip.net.  if you set your account up at www.dyndns.org, you can download a dyndns updater program onto your pc which will automatically update your public IP address with your dynamic dns address, so that you don't have to keep checking your public IP to see if it changed or not.

that's the nuts and bolts of it, assuming you know how to enable your PC for RDP.   hope this helps ya to get it working.  take it easy.

Jim P.
Personally I use LogmeinFREE from http://www.logmein.com it supports nat traversal and with logmein igmition I can log into my computer from ANY WinX machine that is intenet connected.. it definitely supports the KISS (keep it simple stupd) principle.
DONT edit your registry to change the default RDP port, that's NOT a good idea.  USE port forwarding on your router, make the incoming WAN port higher than 10,000 and forward it to your local PC (must use static IP) on port 3389.  Make sure your workstations firewall is accepting traffic on 3389 (TCP).

AGAIN, DON'T change your default RDP port!!!

Also, this is not encrypted, which means someone who happens to be port scanning and picks up this connection may do a man in the middle and grab your plain text password.

ve3ofa- suggestion of an SSL VPN is the best answer if you're doing this for remote access, forget about RDP and opening ports and IPs, it's not what they're there for...
1. Get some DynDns from www.Dyndns.org
2. install some Dyndns Tool which updates your ip to some before choosen link like: myhome.dyndns.org
    or check if your router has such a tool implemented then just config the dyndns over there ( username, pass, done)
3. port forwarding to your local machine something like 3389 -> 192.168.0.2 ( where 192.x is your local ip )
4. Check under -> SYSTEM if your RDP is active at all.

the more secure way...do the same stuff like above, BUT use VNC instead of RDP.

Do not forget to open port 3389 in a Windows Firewall. After that, it should work just fine.
I would also look at some free alternatives to remote desktop like team viewer and logmein.
For default Windows Remote Desktop Port : 3389
Dont forget switch off firewall
Never ever publish rdp to the internet. Install some openvnc or whatever tool, but not rdp. 2nd you should better allow vpn connection to this network and THEN you should connect with rdp within your network.