Summary: Windows XP Pro includes functionality to access the computer's desktop across a network. Remote Desktop must be enabled and configured properly.
How Can I access my Windows XP Machine Remotely?
Terminal Services and Remote Desktop that are available in versions of Windows NT, 2000, XP and 2003 are all about accessing your machine remotely via your network connection. Across the room or across the country it's almost like being right there.
Both Terminal Services and Remote Desktop allow you to connect to a Windows machine over a network net and get a full desktop. It's almost like being at the real console. In fact it's so close that it's allowed many people using multiple computers to set some up without any monitor or keyboard installed at all and use remote access only.
•
Terminal Services, originally code named "Hydra" after the many-headed beast of Greek mythology, is a technology incorporated into Windows NT servers that allows multiple clients to connect to the machine at the same time. Each connection creates a new "virtual" desktop complete with all the icons and menus that you'd see if you had actually logged on on the machine's console. The only downside is that prior to Windows 2003 Server you could not actually log into the actual console remotely.
Enter Remote Desktop in Windows XP Pro. Remote Desktop uses similar technology to allow you to log into a machine remotely but you can only log into the one true desktop - there is only one session. If you log in remotely using Remote Desktop, then the console session is disconnected. Conversely if you log into the console then any remote session will be disconnected. The good news is that if you log in using the same account applications remain running and you can effectively "move" the console to a remote connection and back again.
Windows 2003 server allows for both types of access: additional sessions and Remote Desktop.
In either case the keys to accessing a machine remotely are:
The machine you want to connect to must have either Terminal Services or Remote Desktop sharing installed and running.
The machine you want to connect from must have the Terminal Services or Remote Desktop client installed. The Remote Desktop client is included in Windows XP and can also be downloaded for free here. It can be used to connect to both Terminal Services and Remote Desktop.
When you run Remote Desktop Client you'll specify the name of the machine to connect to and possibly some options controlling the connection. As long as you can "see" the other machine - meaning it's on your local LAN or behind some kind of firewall on the internet then the client connects and you'll be presented with the very familiar logon screen from that machine. Logon and you're there.
Once connected you can do anything remotely that you could if you were sitting at the machine with two very important exceptions:
If the machine is truly physically remote from you then you will not be able to do things like insert a CD-ROM or other physical things.
Windows must be running which implies that you cannot remote-desktop to the boot sequence or to change BIOS settings.
As I mentioned earlier, you can happily use remote desktop across the internet as long as the server is not protected by a firewall such as a broadband router. If it is and your firewall or router supports it you can open port 3389 on the firewall and forward that to the machine you want to connect to. Note that if there is more than one machine behind the firewall then only one can be connected to across the firewall this way.
And finally, Microsoft has a "how-to" article on setting up and using Remote Desktop on Windows XP here.
Article C1871 - December 21, 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Use Hamachi to set up a VPN between the machines:
http://ask-leo.com/recommendation_hamachi_simple_remote_access_vpn.html
Leo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFH/PhNCMEe9B/8oqERAnAGAJsHdgTOtVJw733c4IpAN2DtaDLLNQCcD18j
Posted by: Leo A. Notenboom at April 9, 2008 10:09 AMH/amaJMegrW1D574jxSNMDw=
=4EYj
-----END PGP SIGNATURE-----
my office pc using sify broadband & home pc using bsnl broadband can those connect as remote desktop.
Posted by: Samar at July 8, 2008 4:11 PMI am in pakistan and i want to take the access of my window 2003 server in america,i have no public IP.what should i do???either terminal services require public IP or not???help me
Posted by: Abdul Shakoor at July 25, 2008 10:18 AMHi Sir, I want to connect remotely at my grandfather's PC in U.S.A. and I'm here in Philippines. We're both using a router. How & where can I configure the port 3389 in the firewall? Thank you very much...
Posted by: Aner at July 31, 2008 12:29 AMPlease let me know how can i access my home desktop through the my laptop both is connected with internet.because i want to keep my laptop data to my laptop with the sharing of drive.
Posted by: shambhu prasad at September 22, 2008 3:58 AMplease help me and send all procedure.
IN MY OFFICE ONE XP MACHINE TRATE AS SERVER AND ON THAT MACHINE FOXPRO APPLICATION STORED , MY USER WANT TO ACCESS THAT APPLICATION AND RUN FROM HIS PC , HOW TO CONFIGURE THIS, SHARING FOLDER FROM ANOTHER MACHINE LIKE CONCEPT
Posted by: SANJAY at September 24, 2008 8:22 PMHello, I have a Windows Vista system at home with RDP software and services enabled and right now I am at office. I have the public IP that my ISP has given me. From office when I start the RDP software, in the computer name box i type my IP, when I click connect, after 5 seconds it says could not connect as the server might be bust. Any detailed description on as how to do all this. Both systems are on entirely different networks, gateway is not same and I am not using VPN.
Posted by: Uttam at October 1, 2008 4:58 AMGday, none of the above discusses how one gets past the internet interface (router/modem). I have a Zyxel Prestige 2000 router and an ADSL connection. I have adjusted the firewall to allow all IP access from the WAN and for it to pass through to a PC on my LAN – the PC has IIS running and has an index page in place.
My problem is that when I access the router from the internet side all I get is the logon screen for the router – no pass through to the PC at all. What am I doing wrong? H E L P!
25-Oct-2008
Dear Sir,
Posted by: Rajesh.R.V at December 5, 2008 10:52 PMI want access the client machine deskop on my system.the team viewer is use to one-to-one process.I want one-to-many.Pls Help.Thank u.
Regards,
R.V.
Possible Solution: For those using a VPN either at work or at home, you may need to download Cisco VPN Client or similar to manage your VPN connections. Also, you will need your router to authenticate traffic as this is a job typically handled by the modem. This can be done by logging in to your modem properties and selecting "enable transparent bidge" or simply "enable bridge mode". If your VPN is monitored offsite by a third party, then you will need a UID and PW for the Client software. Without any VPN's in place, you need your target machine to have a Static IP and this will need to be setup in your router as well. Router Setup guides can be easily found online. For small to mid-size business applications I recommend the Cisco 7200 series and for home a Linksys or NetGear would be fine. I hope this helped and I welcome any corrections to any mistakes I may have made. Thank You.
Posted by: Kevin Keyes at February 3, 2009 12:56 PM