July 24, 2008 01:39am pdt

1. and235100 817,467
2. KCTS 545,555
3. slam69 535,119
4. LeeTutor 396,600
5. flubbster 380,929
6. johnb6767 261,744
7. orangutang 257,133
8. nobus 212,209
9. garycase 208,438
10. Jonvee 182,282
11. Merete 180,221
12. rindi 175,306
13. war1 165,697
14. jcimarron 130,376
15. RobWill 129,459

1. Sheharya... 3,649,861
2. LeeTutor 3,047,958
3. sramesh2k 1,985,035
4. and235100 1,951,008
5. war1 1,720,194
6. johnb6767 1,716,358
7. sirbounty 1,526,088
8. Merete 1,402,792
9. KCTS 1,362,330
10. CrazyOne 1,345,842
11. nobus 1,019,493
12. Fatal_Ex... 955,392
13. Kenneniah 925,190
14. sunray_2003 893,020
15. leew 850,561

08.25.2003 at 06:24AM PDT, ID: 20719173

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.4

Windows XP Remote Desktop PORT???

Zone: Windows XP Operating System

Tags: port, remote, desktop

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!

Start your free trial to view this solution

Question Stats

Zone: OS

Question Asked By: js23847

Solution Provided By: PeteLong

Participating Experts: 15

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
Automotive
New Net Users
New Users

Software
Digital Music
Gaming World
Home Security

Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Displays / Monitors
Handhelds / PDAs
Components
Peripherals
Laptops/Notebooks

Servers
Misc
Apple
Embedded Hardware
Networking Hardware

Storage
Desktops
New Users

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMware
Misc
Web Development

OS
CYGWIN
Voice Recognition
Virtualization
Message Queue
Quality Assurance
Security
Firewalls

MultiMedia Applications
Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals
Devices

Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
Web Computing
WebApplications
IDS
Vulnerabilities
Email Clients
File Sharing

Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Consulting
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMware

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel
Automation

Algorithms
Game
Signal Processing
Project Management
Open Source
Database

Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Web Services

Images
Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration

WebApplications
Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Web Computing

Broadband
Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Lounge
Business Travel
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles
Automotive

Community Support

Suggestions
New to EE
New Topics
CleanUp

Announcements
General
Feedback

Input
EE Bugs

08.25.2003 at 06:38AM PDT, ID: 9216063

Rank: Sage

PeteLong:

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

08.25.2003 at 06:49AM PDT, ID: 9216145

js23847:

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

08.25.2003 at 06:58AM PDT, ID: 9216200

Rank: Sage

PeteLong:

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

Accepted Solution

08.25.2003 at 07:03AM PDT, ID: 9216234

Rank: Sage

PeteLong:

:0) ThanQ

02.13.2004 at 08:53AM PST, ID: 10353848

sussertown:

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?

02.24.2004 at 04:30AM PST, ID: 10440135

yellowskyfish:

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.

08.16.2004 at 07:50AM PDT, ID: 11810665

tsorensen55:

Port 3389 is the proper port for remote desktop.

09.20.2004 at 12:24PM PDT, ID: 12105632

luboff:

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.

03.09.2005 at 07:24PM PST, ID: 13502793

albiemanmike:

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.

04.06.2005 at 06:01AM PDT, ID: 13716232

rdong:

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.

05.07.2005 at 08:03AM PDT, ID: 13950803

dcraige27:

RDP port 3389

05.19.2005 at 05:05PM PDT, ID: 14041557

Dongle_Dave:

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

05.21.2005 at 07:03AM PDT, ID: 14051812

dcraige27:

yes 123.23.123.44:3389

06.03.2005 at 07:30PM PDT, ID: 14144387

hswiseman:

"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.

06.17.2005 at 08:58AM PDT, ID: 14242291

rwfleming:

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

neopumpkin

12.05.2007 at 07:52PM PST, ID: 20417270

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.

ve3ofa

12.18.2007 at 06:41PM PST, ID: 20497209

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.

AllCC

02.01.2008 at 11:16AM PST, ID: 20799660

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...

MaurizioSchmidt

02.21.2008 at 03:34AM PST, ID: 20946677

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.

20080236-EE-VQP-29