Workaround 3: Run Remote Desktop Connection (mstsc.exe) Simulated as Another Operating SystemĪnother 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. See the guide to change default Remote Desktop Terminal Services listening port, and how to connect using non-default port in Remote Desktop Connection. By default, Remote Desktop listens and connects on port 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. Workaround 2: Connect to RDC Terminal Services at Different Non Standard PortĪnother workaround to the blockage of local host Remote Desktop connection in Windows is to connect to localhost (127.0.0.1) address on another port other than the default (3389).
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. The trick works in Windows XP Professional and Media Center Edition (MCE) prior to Windows XP Service Pack 2 (SP2), and may also works in Windows 7 or later OSes. Workaround 1: Connect Remote Desktop Connection (RDC) to 127.0.0.2 There’s a few workarounds and hacks that enable user to use Remote Desktop to connect to local PC for another desktop session. 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. It’s Remote Desktop behavior in Windows operating sytem to explicitly prevent and refuse connection from localhost or 127.0.0.1.
0 kommentar(er)
