G
Guest
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!
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!