How to Enable Windows to Make and Accept a Remote Desktop Connection
Information
This tutorial will show you how to enable Remote Desktop Connection, and to connect remotely in Vista, Windows 7, and Windows 8.
Warning
While all editions of Vista, Windows 7, and Windows 8 can be a remote desktop client...
Only the VistaBusiness, Ultimate, and Enterprise editions can host a remote desktop connection.
Only the Windows 7Professional, Ultimate, and Enterprise editions can host a remote desktop connection.
Only the Windows 8Pro and Enterprise editions can host a remote desktop connection.
FIRST
To Enable Remote Connection
1. Go to Control Panel>System>Advanced System Settings
2. Go to Remote tab.
3. Under Remote Assistance, put a check mark on Allow Remote Assistance connections to this computer. Note:This automatically adds Remote Desktop exception to Windows Firewall.
4. Click on Apply.
OPTION ONE
To Connect to a Remote Desktop (Local Area Connectivity)
1. Go to Start>All Programs>Accessories>Remote Desktop Connection NOTE:You could also press the Windows + R keys to open the Run dialog, type mstsc.exe, and press Enter.
3. For more connection options, click on Options NOTE:Here you can save the connection profile, adjust display properties, run specified programs upon connection, adjust connection bandwidth, etc. For more information on specific tabs, click on Help.
4. Click on Connect.
5. Enter your log in credentials of a user account on the remote computer that is allowed to do a remote desktop connection.
OPTION TWO
Enable Windows to Accept Remote Desktop Connection (Local Area Connectivity)
1. Go to Control Panel>System>Advanced System Settings
2. Go to Remote tab.
3. Under Remote Assistance, put a check mark on Allow Remote Assistance connections to this computer Note:This automatically adds Remote Desktop exception in Windows Firewall.
4. Click on Advanced...
5. Put a check mark on Allow this computer to be controlled remotely.
6. Click on OK. Note:This automatically adds Remote Assistance exception in Windows Firewall.
7. Remote Desktop Connection behind a router (Single computer)
A) Configure your router's port forwarding to allow connections on port 3389
B) Now in RDC just type the IP address supplied by your ISP
8. Remote Desktop Connection behind a router (Multiple computers)
A) For each computer you want to remotely connect to you have to configure each computer to listen to different ports to avoid port conflicts by changing the registry key in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
B) Port Numbers are in Decimal format Note: To avoid conflict with other programs it is suggested to select a port between 49152 and 65535.
C) Now take that number you've chosen your computer to listen to and configure your router to port forward to that number
D) To connect to that computer your format will now be ISPIPAddress:PortNumber (ex. 222.222.2.8:1234) to connect to that specific computer behind the router
Important: If you have a firewall software running, that too has to be configured to allow communication to the port you opened in your router as well.
Note:The above steps assumes that you're not part of a domain.
System Manufacturer/Model Number Tx2500z Tablet Pc/Homemade Server OS Windows 7 Ult x64(x2), HomePrem x32(x4), Server 08 (+VM), 08 R2 (VM) , SuSe 11.2 (VM), XP 32 (VM) CPU Turion X2 ultra (oh well came with laptop)/P4 @3.2 (yes P4) Motherboard IDK HP Motherboard / Intel DG965SS Memory OCZ Dual Channel 4GB kit/ 1gb Dual Channel Graphics Card HD 3200 graphics /GMA x3100 (yay for intergrated!!) Sound Card Realtek HD Audio(mic working, well sort of)/Siig IC-70012 Monitor(s) Displays built-in Hp 12" laptop screen/ Acer 19" Screen Resolution 1280x800 /1440x900
Mouse Logi MX Rev. /MS Wheel Optical 1.1A /Logitech Optical Mouse Cooling All Air Cooled Internet Speed College baby but its still routed through vpn to 1536k... Other Info love my wacom pen and pressure sensitivity...
wished it worked in 7, SUSE for that matter though
For the multiple computers step.... is that if you want multiple simultaneous connections on different stations on the lan?
What about with the same scenario, with incoming connections outside the lan. You would have to configure the router for each specified computer as well.
Something else thought up to complicate. What about a large lan with different pcs on different subnets. how would one pc find another on a different subnet? IP, name, or would you do better by setting up domains?
Am thinking you would/could have to port the 3389 to a different port for the switch of the different subnets. Useful if you dont want alot of bottlenecking in a particular area of the LAN. Allowing only one session to a grouped subnet while allowing multiple simultaneous sessions on another.
Hmmm... Nos, why is there a reason to do this reg hack in seven when MS released a RD 2.0 for macs that allow simultaneous connections to multiple windows based machines? Shouldnt this be available for 7 as well? Or is this a TS issue? If so, this is ludacris IMO
System Manufacturer/Model Number CUSTOM OS XP/win7 x86 build 7127 CPU Athlon64 X2 DUAL 4200+ 2.21ghz Motherboard ASUS K8 PRO SLI Memory 2GB Dual Chan DDR2 Corsair Graphics Card Nvidia 6800GT Sound Card nvidia Monitor(s) Displays 19' LCD Screen Resolution 1280x1024
Keyboard MS wireless Mouse MS Wireless PSU coolermaster 450 Case SUPERFLOWER Cooling 1 HDD bay fan, 5x80mm Case Fans, AEROGATE II Fan/Temp Hard Drives WD 250, 2x500, 2x1TB IDE/USB
WD 250 SATA (system)
SEAGATE 120 Sata Internet Speed fassssssssst
For the multiple computers step.... is that if you want multiple simultaneous connections on different stations on the lan?
No. That step is for simultaneous connections behind a router.
As long as all the computers are on the same network, multiple connections to different clients can easily be accomplished. Just open a different instance for each client you want to connect to.
Quote: Originally Posted by Digger
What about with the same scenario, with incoming connections outside the lan. You would have to configure the router for each specified computer as well.
Yes.
Quote: Originally Posted by Digger
Something else thought up to complicate. What about a large lan with different pcs on different subnets. how would one pc find another on a different subnet? IP, name, or would you do better by setting up domains?
Am thinking you would/could have to port the 3389 to a different port for the switch of the different subnets. Useful if you dont want alot of bottlenecking in a particular area of the LAN. Allowing only one session to a grouped subnet while allowing multiple simultaneous sessions on another.
As long as the different subnets are designed to communicate with each other, this wouldn't be a problem.
On a large corporate network, that have different/numerous subnets, even if it's geographically diverse, you would only need the Fully-Qualified Domain Name (FQDN) of the computer you need to gain access to or it's IP address, although in a large corporate environment, the use of IP addresses is not encouraged as IP leases are renewed regularly, regardless if its a desktop, laptop or mobile device.
Quote: Originally Posted by Digger
Hmmm... Nos, why is there a reason to do this reg hack in seven when MS released a RD 2.0 for macs that allow simultaneous connections to multiple windows based machines? Shouldnt this be available for 7 as well? Or is this a TS issue? If so, this is ludacris IMO
Regardless if its a Mac or a PC, the same rules apply when connecting to RDC Clients. Multiple connections apply to Mac host wanting to access multiple PC clients and vice versa easily as long as they're on the same network/domain.
I hope I've answered the questions satisfactorily. If you do have further questions or you'd want a more detailed explanation regarding the matter or other networking questions, I'd be most willing and happy to answer them for you.
I hope I've answered the questions satisfactorily. If you do have further questions or you'd want a more detailed explanation regarding the matter or other networking questions, I'd be most willing and happy to answer them for you.
Cheers
Yes, answered very well Nos, thanks for the response. Yet to work with this in seven, and seen your tut and did some googling around. Nice job btw
System Manufacturer/Model Number CUSTOM OS XP/win7 x86 build 7127 CPU Athlon64 X2 DUAL 4200+ 2.21ghz Motherboard ASUS K8 PRO SLI Memory 2GB Dual Chan DDR2 Corsair Graphics Card Nvidia 6800GT Sound Card nvidia Monitor(s) Displays 19' LCD Screen Resolution 1280x1024
Keyboard MS wireless Mouse MS Wireless PSU coolermaster 450 Case SUPERFLOWER Cooling 1 HDD bay fan, 5x80mm Case Fans, AEROGATE II Fan/Temp Hard Drives WD 250, 2x500, 2x1TB IDE/USB
WD 250 SATA (system)
SEAGATE 120 Sata Internet Speed fassssssssst
In my research I found references that remote access to a WIN 7 machine will only be available in the PRO version.
I downloaded the WIN 7 RC (I believe is the home version) and set up all the above settings to allow remote access. When I try to access the machine (from an XP machine on the same inhouse network) I get the the login screen asking for USER NAME and PASSWORD. I entered the User Name and Password that I use for a direct login on the machine and get a message that either User Name or Password are incorrect. Am I missing something in the setup?
hi, does anybody know if it is possible to login on same computer using different accounts at the same time?
i would like to use my computer though remote connection, while anyone else use it.
i did all steps in the tutorial, but currently Windows 7 asks local user to disconnect when i'am logging in via remote desktop
Information
Warning
FIRST 
Quote: Originally Posted by Digger 
Remote Desktop Connection 
