Windows XP Pro as a client of Remote Dekstop via stunnel

Hi! I'm currently working (without success) on such problem: I have to connect via Stunnel to Windows Server Remote Desktop from workstation with Windows XP Proffesional. When I refer to the local port handled by stunnel, Windows doesn't let me go go further, because it thinks that I'm trying to use local Remote Dekstop and prints: "You are already connected to this machine" (there can be only one connection through RD) . Is there any workaround for this problem, namely, to use secure connection via Stunnel to Remote Dekstop on XP Pro client? This is my config: client=yes cert = stunnel.pem [ts] accept=localhost:3389 connect=remote_ip:443

Given that Remote Desktop is a secure connection, why would you have to do Stunnel in addition? --On Wednesday, March 02, 2005 12:17 +0100 Jacek Baszkiewicz <banys@op.pl> wrote:
Hi!
I'm currently working (without success) on such problem: I have to connect via Stunnel to Windows Server Remote Desktop from workstation with Windows XP Proffesional. When I refer to the local port handled by stunnel, Windows doesn't let me go go further, because it thinks that I'm trying to use local Remote Dekstop and prints: "You are already connected to this machine" (there can be only one connection through RD) . Is there any workaround for this problem, namely, to use secure connection via Stunnel to Remote Dekstop on XP Pro client? This is my config:
client=yes cert = stunnel.pem
[ts] accept=localhost:3389 connect=remote_ip:443 _______________________________________________ stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users

On Wed, 2 Mar 2005, Jacek Baszkiewicz wrote:
I'm currently working (without success) on such problem: I have to connect via Stunnel to Windows Server Remote Desktop from workstation with Windows XP Proffesional. When I refer to the local port handled by stunnel, Windows doesn't let me go go further, because it thinks that I'm trying to use local Remote Dekstop and prints: "You are already connected to this machine" (there can be only one connection through RD) . Is there any workaround for this problem, namely, to use secure connection via Stunnel to Remote Dekstop on XP Pro client? This is my config:
Either shutdown your local Remote Desktop client (don't know what will break then) or let your stunnel listen on 127.0.0.2:3389 and have your remote desktop client connect to that. Jan -- http://www.surfnet.nl/organisatie/jame

Hello, Windows XP doesn't allow you to form terminal services connection to the loopback address regardless of the port. Take a copy of MSTSC.EXE (from c:\windows\system32) to somewhere on the machine and change the compatibility mode to Windows 98 - this works fine with my stunneled and non-stunneled terminal services connections. Regards, Mike -----Original Message----- From: stunnel-users-bounces@mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Jacek Baszkiewicz Sent: 02 March 2005 11:17 To: stunnel-users@mirt.net Subject: [stunnel-users] Windows XP Pro as a client of Remote Dekstop viastunnel Hi! I'm currently working (without success) on such problem: I have to connect via Stunnel to Windows Server Remote Desktop from workstation with Windows XP Proffesional. When I refer to the local port handled by stunnel, Windows doesn't let me go go further, because it thinks that I'm trying to use local Remote Dekstop and prints: "You are already connected to this machine" (there can be only one connection through RD) . Is there any workaround for this problem, namely, to use secure connection via Stunnel to Remote Dekstop on XP Pro client? This is my config: client=yes cert = stunnel.pem [ts] accept=localhost:3389 connect=remote_ip:443 _______________________________________________ stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.5.7 - Release Date: 01/03/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.5.7 - Release Date: 01/03/2005

Apply this patch, if you use Windows XP SP2, then it should work fine. http://support.microsoft.com/default.aspx?scid=kb;en-us;884020 If you didn't apply SP2, Windows XP does not allow 127.0.0.1:3389 access. Use another loopback range address, such as 127.0.10.10, or listening a different port like 3390, then it should work. regards
participants (5)
-
ikeda@areabe
-
Jacek Baszkiewicz
-
Jan Meijer
-
Mike Ollington
-
patrick daniels