Remote Desktop: At Your Desk While on the Road

Access your XP Pro PC from anywhere

You've finally arrived at your hotel room, and you're ready to relax before giving your important presentation tomorrow. But when you open your laptop, you realize that you forgot to transfer the current version of your presentation from your Windows XP Professional Edition home or office computer to your mobile machine. No one's at home to email you the file. Unless you can find some way to access the file, you've got a long night ahead of you.

But if you've installed the Remote Desktop Connection client software on your laptop and enabled XP Pro's Remote Desktop feature on your home or office system, you're in luck. You can use this single-user version of Windows Terminal Services to log on remotely to your home computer—access it as if you were sitting at your desk—and copy the presentation to your laptop's local hard disk. Remote Desktop can give you remote access—complete with full color and sound—to local disk drives on an XP Pro workstation. You can copy files between computers that aren't on the same network, or you can access a powerful but inconveniently located system from a less powerful but mobile machine.

Windows Terminal Services 101


During the past few years, Microsoft has begun to embrace the benefits of multiuser computing. Terminal Services is a core service in all Windows 2000 Server products. Until XP, Terminal Services worked in this way: Users at desktop client machines ran applications that resided on the server (called the terminal server) and displayed the output on the client. Win2K and later server products support Terminal Services in one of two modes: Remote Administration mode, which gives administrators remote control of a server, or Application Server mode, which lets users run applications from the server. Remote Administration mode permits as many as two remote administrative connections in addition to the server's console connection; Application Server mode permits as many simultaneous connections as the server license specifies.

In a Terminal Services environment, client computers connect to a terminal server through a display protocol that sends graphical output to the client's monitor and accepts keystrokes and mouse clicks from the client. The native Windows protocol is RDP; RDP 5.0, which Terminal Services uses, supports automatic client-printer mapping and a shared clipboard that lets users copy text between sessions or between local and remote applications. However, RDP 5.0 has a 256-color display limit, doesn't provide sound support, and doesn't map client-side drives to the terminal session.

All earlier versions of Terminal Services were limited in that you could use them only when you bought a server OS—you had no way to get Terminal Services functionality on a personal OS. With the release of XP Pro, Terminal Services functionality has finally reached the desktop. Through its Remote Desktop feature, XP Pro uses Terminal Services to provide remote access to a PC.

Ready for Remote Desktop


Remote Desktop provides single-connection remote access to the computer. This setup is similar to Terminal Services in Remote Administration mode in that you don't need to purchase extra licenses to use it. However, Remote Desktop permits only one remote connection and either shuts down the host system's local console when someone launches a remote session or shuts down the remote session when someone logs on to the console. (If, for example, you use an account name to log on at the console, then later use the same account name to connect remotely, Remote Desktop automatically shuts down the console session. If you use a different account name to connect remotely, Remote Desktop warns you that continuing will lock out another session and asks whether you want to continue.)

XP Pro doesn't permit incoming Remote Desktop connections by default. To configure a host system to accept incoming connections, open the Control Panel System applet and go to the Remote tab, which Figure 1 shows. Select the Allow users to connect remotely to this computer check box, then click OK. Enabling remote connections doesn't give all users automatic access to the host computer: The setting simply lets members of the local and Domain Administrators groups initiate an RDP session and provide their logon credentials.

You can permit accounts outside of these groups to use Remote Desktop. On the Remote tab, click Select Remote Users to see a list of permitted Remote Desktop users. To add users to this list (which will be empty at first), click Add to open the Select Users dialog box. Choose the source of the accounts you want to add (you can choose from computer-based accounts or from domain accounts if the XP system is part of a domain). If you know the exact name and spelling of the account you want to add, enter the name as ComputerName\UserName or DomainName\UserName (click the Examples link to see examples of the correct formats). If you don't know the exact name, click Advanced, then click Locations. Choose the computer or domain that you want to browse, then choose the type of object you want to browse for (Users only for computer-based accounts or Users and/or Groups for domain accounts). Click Find Now. The area at the bottom of the dialog box will populate with the applicable account objects from the chosen location. Select the account or accounts that you want to add (you can use the Ctrl key to select multiple accounts), then click OK. Click OK again to close the Select Users dialog box. The chosen accounts now appear in the permitted users list.

XP's RDP protocol is the Remote Desktop Connection client. XP Pro and XP Home Edition automatically install the client on a system during OS installation. To use Remote Desktop Connection on earlier Windows systems, you can install the Remote Desktop Connection client from the XP CD-ROM, or you can download that client (for free) from Microsoft at http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp. The 3.4MB download file is called msrdpcli.exe file. Run this file and follow the installation wizard to accept the license agreement, choose whether Remote Desktop Connection should be available for all people using the computer or just for the person installing the client, and install the support files. Installing Remote Desktop Connection on a Win2K or Windows 9x computer permits you to connect to another computer; the client doesn't permit other computers to connect to your system.

After you install Remote Desktop Connection, connecting to the remote XP computer is easy. Select Programs, Accessories, Communications, Remote Desktop Connection to open the Remote Desktop Connection dialog box. Type the name of the host system in the Computer text box, then click Connect. The connection automatically opens in full-screen mode, and the host computer's desktop completely replaces the local desktop at the local resolution. To see your local desktop, move the mouse to the upper center of the screen. A tab with the name of the host computer appears alongside the typical window-manipulation buttons (i.e., Minimize, Resize, Maximize, and Close). You can use these buttons to minimize the remote session to a Taskbar button, resize the remote session to display in a window, or close the session window. Closing the window disconnects but doesn't terminate the remote session. You can use the same procedure you used to create the session to reconnect to the session and continue where you left off. (For instructions about shutting down a session, see the sidebar "Remote Desktop Troubleshooting Tips.")

Configuring Remote Desktop Connection


You can also configure expanded Remote Desktop Connection settings. To do so, open Remote Desktop Connection and click Options to expand the Remote Desktop Connection dialog box.

Remote Desktop Connection uses your logon credentials to connect to the remote computer. If those credentials don't work (perhaps because you don't have a user account on both computers), you can add the proper credentials on the General tab, which Figure 2 shows. From this tab, you can click Save As to save connection settings and copy them to another computer on which Remote Desktop Connection is installed. (To use saved settings, click Open.)

The Display tab contains—you guessed it—display settings. When you want to view the remote session in a smaller window rather than in the default full-screen mode, or if your session is slow over a dial-up connection when using 24-bit color, you can edit those settings on the Display tab to put less stress on the connection.

The Local Resources tab controls communication between the local computer and the remote system. If you want to automatically map the local computer's drives to the remote system or use the local computer's COM port with the remote session, you can enable those capabilities on this tab. (You can also disable these features from the Local Resources tab.) You can configure sound and keyboard shortcut settings on this tab.

If you plan to use Remote Desktop Connection to run only one application on the remote computer, you can enter the application's path on the Programs tab. (You must know the path. The tab doesn't offer a Browse option because you aren't yet connected to the remote computer.) When you enter the path, the remote application is started and maximized automatically when you log on to the remote session. Closing the remote application disconnects you from the remote computer.

The Experience tab lets you specify your connection's speed and thus selectively enable or disable features such as menu and window animation. You can enable or disable these settings individually, but at first you might want to stick with the client's suggested settings to get the best performance from each network speed. Enabling too many options over slow connections can make your remote session sluggish.

Don't Leave Home Without It


Setting up XP's Remote Desktop and using the feature to connect to an XP Pro system truly is as easy as it sounds. (See the sidebar "Remote Desktop Troubleshooting Tips" for the answers to potential questions and snags.) Of course, Remote Desktop doesn't provide the Terminal Services support of a Windows terminal server, but the feature still provides a handy and easy way to access your host computer. You'll feel as if you never left home.

Discuss this Article 45

Jeff (not verified)
on May 19, 2004
This article on Remote Desktop is very informative and well written. An order of thanks is due to the author, not bashing. There's no way Christa could address every home computer network design and how one connects from external locations. If someone built a home network, they should know how it works and know how external connections are granted and denied. If one doesn't know the basics, better to unplug it. RDP establishes connection over port 3389. If you have a host-based or appliance-based firewall, all external WAN requests to connect to port 3389 will be denied by default. This is a good thing. As one commenter mentioned, those who use an appliance-type firewall will need to create a rule to port forward 3389 requests to an internal IP address (the XP computer). Those who use host-based firewalls will need to create a rule that allows incoming port 3389 connections. The risk you must accept is EVERYONE on the Internet can attempt to connect to your computer once this port 3389 hole is opened. The only exception to this would be if you knew the source IP address and restricted connections to that address in the firewall settings. If you're on travel, it's not likely you'll know that IP address in advance. If you're on a corporate network and trying to connect to your home computer, chances are the corporate firewall is not allowing RDP 3389 communications, as it should be. Now, suppose you successfully open incoming 3389 to your home XP computer. You should also set your computer security policy to lockout the account after 3 bad sign-in attempts. The lockout should be for 15 or 30 minutes. This will prevent a brute force attempt to crack your password. While you're at it, rename the administrator account to adminsky or whatever. If the hacker attempts a brute force attack, don't let him have the first part of the equation, which is the name of the default administrator account. For those of you who have a home LAN with more than one computer, the answer is simple. Port forward 3389 to one computer as discussed. Once you RDP in to that one computer, run Remote Desktop on that computer, then connect freely to any computer on the LAN that's RDP enabled per the above article. Now, think about whether Remote Desktop is transmitting your data over the Internet in the clear. It would be wise to make sure the encryption security policy is set on the Remote Desktop client. Jeff FedSpell.com Free Spell Checker for Internet Explorer
joe (not verified)
on Aug 2, 2006
RDP is the greatest! I use to use PC Anywhere back in the old days - but not anymore. XP-Pro RDP is far supperior! I use it to control my network at work from home or on the road and and even use my PDA now to do so. I use it to get into my home network from work. It is easy to setup and use. Home routers are a problem for those that do not understand TCP/IP networking procedures but if you read your user manual for your router (LINKSYS NETGEAR D-LINK ect) you can figure it out! I agree that the author did a great job in descibing the wonderful advantages of RDP. Ultra VNC is also a close contender but I like RDP better. Thank you!
Ken Posey (not verified)
on Aug 12, 2006
Very good article on RDP. I have used it for some time and also use Ultra VNC on my other machines running XP Home Edition. I recently encountered a problem with a public access at a hospital where neither RDP nor Ultra VNC would work. The host system apparently blocks them. Is it likely a simple matter of the host being configured to block port 3389? I want to send feedback to the admin of that sytem but I am ignorant of what advice to give should they wish to allow RDP or similar routines to work through their system.
prem (not verified)
on Aug 17, 2005
I want to allow more than two users to connect to my Win 2003 Server simutanuasly, which is restricted for 2 connections at a time. Please help me on this.
jos (not verified)
on Aug 10, 2004
Your Comments (required):
Don
on Mar 29, 2006
concurrent remote desktop session can be acchieved in windows XP pro. Google it!
mason anderson (not verified)
on Jan 12, 2008
Hi, I got a system off a friend… it’s a Compaq dc7600. Tried to log on but every time I do enter my user name and password it says CLOSING NETWORK CONNECTION. It’s got nothing to do with the password or username, definitely know that for a fact. When I’m entering the user name and password, there’s also a LOG ON TO option after password. Id appreciate it if I could get sum assistance. thanx
JuL (not verified)
on Apr 25, 2004
Not quite that simple. On a LAN behind a NAT router (typical DSL sharing configuration) there is no way - even with UPnP - for the router to know to which LAN computer it should redirect WAN Remote Desktop connections. Therefore you have to manually configure the router to redirect Remote Desktop connection attemps to the desired computer. And if you have more than one, you have to change the default Remote Desktop port, so that each computer on the LAN use a different one. JL.
Ajith (not verified)
on Jul 20, 2005
I have a querry. I am trying to login into my Win2k Advanced server, but it is not allowing to do so. Even when I am siiting on the server it says server has closed network connection. Could u help me sort out this problem. Regards Ajit
Shoaib (not verified)
on Jul 17, 2006
Sir i want to connect desktop connection to my home pc ie mstsc please tell me about mstsc feature in detail each step which is involved. i will be very thankful bye
john (not verified)
on Dec 21, 2004
I work in a small office and outsource IT when needed. The IT guy set up a vpn so i could access my work computer from home. Both computers are xp Pro and Linksys dsl router at home and work. I was able to connect vpn to the work network, however, when i try to browse for my computer i can only see my home network. When trying to connect i get the following error "the specified computer could not be found. verify you have typed the correct computer name or Ip address and try connecting again". any ideas??? thanks.
Irv Rollman (not verified)
on May 20, 2002
Did I miss something, or was this article a little light on setting this up for connection through a DSL (or cable, or ???) router? How does one do this?
dada (not verified)
on Dec 9, 2005
in win 2003 server how many users may be connected by terminal service
stan (not verified)
on Feb 3, 2005
anyone got crack win2k server terminal service ?
Steve Ellis (not verified)
on Aug 4, 2005
Very interesting article. I have been using this feature for a few years now but yesterday something wierd happened: I remotely connected to a customer's PC (Win XP Pro) and my session did not blank out her's. I was able to work on a database and she worked sitting at the machine on other files. I have never known this happen before. We both used the same user account. Does anyone know how this could happen? Steve Ellis Shipley, UK
natarajan (not verified)
on Oct 25, 2006
just
Randy D (not verified)
on Sep 8, 2004
Excellent article. I have an answer for the person who had trouble using remote desktop with the linksys router. I have a linksys befsx41 router and I had trouble with people connecting to my port 3389 through my fire wall. I first set up port forwarding 3389 to 168.192.1.100 3389 (internal PC with port number). But I still had problems connecting (my PC at work could get in, but not other PCs). I contacted linksys and they suggested upgrading my firmware on my linksys router. I did and it worked fine.
Tony Pritchett (not verified)
on May 14, 2004
I'm in agreement with Jim C. It is NOT EASY as you led us to believe. I've spent extra money on XP Professional (not to mention, time), and I still can't get RDC to work. I've searched the internet for some simple procedure to get passed a linsys router, to no avail. Someone needs to pick this issue up and FIX IT!
sachin (not verified)
on Dec 29, 2005
d-4 remote desktop shearing
Jim Corbin (not verified)
on Jun 12, 2002
Windows XP on the inside of the LAN should automatically configure a router/gateway to handle Remote Desktop, IF the router includes a Universal Plug and Play Internet Gateway Device (UPnP IGD) stack. See http://www.intel.com/home/scenes/news/plug_play.htm, or http://www.intel.com/update/departments/netcomm/nc01021.pdf. Intel is recommending to retailers that they do not stock gateways that do not include UPnP. On non-UPnP routers, you have to determine the correct port mapping and manually configure the device (if that is possible).
anil (not verified)
on Feb 26, 2007
i want to no how it work
jos (not verified)
on Aug 10, 2004
win xp terminal service crack
Alp (not verified)
on Jan 1, 2005
To Jeff: Lots of useful information, thank you. How do you actually rename the administrator account, or any account? As far as I know, when you rename an account either from 'User Accounts' on the control panel or from computer managment (my computer>right click>manage>system tools>local users>users>), it just assigns a new alias to that account (aka 'Full Name'). But the 'name' of the account stays the same. That's the same for administrator account as well. You can now login both with the original username and the new 'Full Name' you just created. So I beleive that this does not provide any extra security. My question is that how do you enable "encryption security policy on the Remote Desktop client" as you suggested in your post. Thanks
Adrian (not verified)
on Oct 22, 2009
"Type the name of the host system in the Computer text box, then click Connect." This only works if you are already on the same LAN or virtual LAN right? I suppose before connecting via RDC the user needs to establish a VPN connection to the same network that the remote pc is on? Or do you mean that the full IP address of the remote pc should be entered as the name?
sachin (not verified)
on Dec 29, 2005
remote desktop shearing

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.