Re: Problem with RDP client v5.2 on Windows XP

I ran into the same problem...It has to do with the downloadable version of
the 5.2 RDP client. Apparently it is an old version that has the loopback
bug in it.

To work around your problem, you can install TS client that comes with
Windows Server 2003 SP1 (if you have one) - or just use the client version
available in XP SP2.

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"circle" <circle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:24FFB990-C468-4B5F-B8C0-83D95D58EA15@xxxxxxxxxxxxxxxx
Hi all,

I have upgraded the RDP client of my box to v5.2 recently. Basically it
works fine, but when I try to connect to some local address (e.g.
localhost/127.0.0.1/IP address of my box), it prompts an error that I am
already connecting to a console session. Here is the full error message:
The client could not connect. You are already connected to the console of
this computer. A new console session cannot be established.

You may wonder why I am trying to localhost. I have built a SSH tunnel to
another PC and I am trying to connect to that PC through this tunnel. So I
connect to the local end point of the tunnel (e.g. localhost:1234, or
192.168.1.100:1234), but both fails. My local RDP service is listening on
the
default port (3389).

I don't have this problem when using the original RDP client. It is also
ok
to do this with RDP client v5.2 on a Windows Server 2003 box. My
observation
is that only using RDP client v5.2 to connect to any local port on Windows
XP
reproduces the problem. From firewall log, there is NO attempt to
establish
any connections in this situation. Seems that the v5.2 client simply
checks
whether the target machine has IP of any of the local interface, and
ingoring
the target port, only on windows xp....

I also triled to connect to non-standard port of remote hosts with RDP
client v5.2 by specifying the port number (e.g. any.host.com:1234), it
DOES
try to establish an connection.

Has any of you meet this problem? Any possible solution/workarounds? Or
would anyone try to reproduce this problem?

any help is appricated! Thanks!

--
circle


.

Relevant Pages

  • Re: Remote Desktop Connection - Unable to view local printer
    ... This is most likely becuase Windows XP comes with a version of RDP client ... (It does not have a LPT Port) ...
    (microsoft.public.win2000.termserv.clients)
  • local printers
    ... I've got a client connecting to a W2k3 server using XP's RDP client. ... having no drivers available, as if the printer doesn't even exist. ...
    (microsoft.public.win2000.termserv.clients)
  • printers through RDP
    ... I've got a client connecting to a W2k3 server using XP's RDP client. ... having no drivers available, as if the printer doesn't even exist. ...
    (microsoft.public.windows.terminal_services)
  • Re: Problem with RDP client v5.2 on Windows XP
    ... The information concerning the use of the W2K3 RDP client on other PCs came ... Al Jarvi (MS-MVP Windows Networking) ... already connecting to a console session. ... default port. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Problem with RDP client v5.2 on Windows XP
    ... I am interested about the license terms of the RDP client come ... Can we use that on other Windows box? ... already connecting to a console session. ... is that only using RDP client v5.2 to connect to any local port on Windows ...
    (microsoft.public.windowsxp.work_remotely)