Workaround for Remote Desktop Client to Connect to Localhost (Local Terminal Server Service)

When user runs Remote Desktop Connection, a RDP (Remote Desktop Protocol, or more commonly known as Terminal Services) client in Windows XP, and attempts to connect to Terminal Server service running on localhost (or using 127.0.0.1 IP address), which is own computer itself, Remote Desktop connection or session is disconnected, or rather unable and cannot connect with following error message.

The client could not connect. You are already connected to the console of this computer. A new console session cannot be established.

It’s Remote Desktop behavior in Windows XP to explicitly prevent and refuse connection from localhost or 127.0.0.1. Connecting remote desktop client to localhost is useful for user who wants to have 2 sessions of desktop, to tunnel Remote Desktop connection through encrypted SSH (Secure Shell), or want to test if the patched termsrv.dll to unlock unlimited concurrent Remote Desktop sessions working or not.

There’s a few workarounds and hacks that enable user to use Remote Desktop to connect to local PC for another desktop session.

Workaround 1: Connect Remote Desktop Connection (RDC) to 127.0.0.2

The trick works in Windows XP Professional and Media Center Edition (MCE) prior to Windows XP Service Pack 2 (SP2). 127.0.0.2 is the internal TCP/IP loopback address and Remote Desktop prior to version SP2 allow connection through the loopback 127.0.0.2 IP address, although it actively blocks connection via 127.0.0.1 or localhost string.

Workaround 2: Connect to RDC Terminal Services at Different Non Standard Port

Another workaround to the blockage of local host Remote Desktop connection in Windows XP is to connect to localhost (127.0.0.1) address on another port other than the default (3389). The hack is especially useful in Windows XP SP2 and SP3 where 127.0.0.2 forwarding IP address for localhost connection no longer work. By default, Remote Desktop listens and connects on port 3389. See the guide to change default Remote Desktop Terminal Services listening port, and how to connect using non-default port in Remote Desktop Connection.

Workaround 3: Run Remote Desktop Connection (mstsc.exe) Simulated as Another Operating System

Another hack to allow Remote Desktop Connection client to connect to localhost is to trick the Terminal Services into thinking that the RDC client is from another operating system, indirectly indicate it’s from another remote computer. To use the trick, follow these steps:

  1. Create a folder such as C:\RDC.
  2. Go to C:\Windows\System32\ folder and copy mstsc.exe and mstscax.dll files to the new folder.
  3. In the new folder, right click on mstsc.exe, and then select Properties.
  4. Go to Compatibility tab.
  5. Tick the check box for Run this program in compatibility mode for option.
  6. Select Windows 98 / Windows Me in the drop down list.
  7. Click on OK button.
  8. Double click on the mstsc.exe in the new folder to run Remote Desktop Connection or Terminal Services client, and now the client can connect to localhost or 127.0.0.1 as computer name.

Note that when logging in in Remote Desktop session, log on as different user or else you may be logging out forcefully.


This entry was posted on Friday, June 13th, 2008 at 1:22 am and is filed under Utilities. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “Workaround for Remote Desktop Client to Connect to Localhost (Local Terminal Server Service)”

  1. Chan Lee Meng
    September 11th, 2008 10:41
    1

    I’m on Vista and I can confirm that the 127.0.0.2 trick does NOT work on Vista.

    The “Non-Standard RDP Port” trick DOES work though. I’m tunnelling using Zebedee, and I just configured it to listen on port 4000 locally and redirect traffic to port 3389 on the other side.

    I did not test the third workaround.

Leave a Reply

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe to comments feature has been disabled. To receive notification of latest comments posted, subscribe to My Digital Life Comments RSS feed or register to receive new comments in daily email digest.
« Download Free KeyJnote to Transform PDF files into Interactive Presentation Foils
Enable Multiple Concurrent Remote Desktop Connections or Sessions in Windows XP »

Custom Search

New Articles

Incoming Search Terms for the Article

your computer could not connect to another console session - the client could not connect. you are already connected to the console of this computer - you are already connected to the console of this computer - the client could not connect you are already connected to the console of this computer - a new console session cannot be established - mstsc localhost - The client could not connect. you are already connected to the console of this computer. - cannot save multiple credentials for the same remote computer workaround - rdp loopback - remote desktop localhost - rdp localhost - remote desktop you are already connected to the console of this computer - the client could not connect. you are already connected to the console - remote desktop loopback - your computer could not connect to another console session on the remote computer - kis 2010 remote desktop - the client could not connect you are already connected - "your computer could not connect to another console session" - the client could not connect. you are already connected to the console of this computer. - "The client could not connect. You are already connected to the console of this computer" - rdp hack show desktop to console user - Connecting to Localhost on XP prior to SP2 - mstsc connect localhost - your computer could not connect to another console session on the remote computer ssh tunnel - rdp loopback address sp3 - android terminal server client - remote desktop client could not connect to the remote computer - remote desktop to localhost - you are already connected to terminal - rdp you are already connected to the console of this computer - rdp "already connected to the console" - remote desktop - couldnt connect to console session - the client could not connected you are already connected to console as the user - you are already connected to the console - remote desktop windows xp localhost - Windows 7 remote desktop localhost - windows genuine local host - your computer could not connect to another console - How do I connect Windows Desktop Client to a remote port other than 3389? - remote desktop connection port local host windows 7 - rdp to localhost - remote desktop error the client could not connect to the remote computer - the client could not connect. you are already connected to the console of this computer. a new console session cannot be established. - how to enable remote desktop in kis 2010 - mstsc cannot connect - rdp from localhost - Remote Desktop and XP SP3 Workaround - remote desktop the client could not connect. you are already connected - remote desktop console can not connect - allow connect to terminal server from localhost windows -