RE: Tunneling Terminal Server Client on WinXP?

>When I try this on an XP Pro machine, however, the TS Client refuses to
>connect to localhost, telling me I'm already at localhost's console.

This is the follow up to an old post, wrt the WinXP Terminal Services
client preventing local connections. Still looking for an answer   :-\


> I'v had the same problem. I'v copied the 'old' terminal client (that
comes with
> Windows2000 server), and put it in a separate directory. This client
allows a
> connection to localhost -> problem solved.

Just copied mstsc.exe from one of our W2K Servers and tried it from both
\Desktop and C:\ -- running "mstsc /v:etc" from the command prompt
displays nothing; you just get a new line and the command prompt appears
again.


> There is also a alternative way (although i'm not sure anymore if it
works). Copy
> the XP terminal client executable to a separate directory.  Right
click the executable,
> select property's and switch to the tab compatibility. Select NT 4.0
or 2000 as OS
> Version.

Tried this using all the compatibility modes available, but still get
the "The client could not connect. You are already connected to the
console of this computer..." message.


> This is caused by the fact that WinXP includes a small 'Terminal
Server' as
> a native feature. In WinXP this is known as 'Remote Desktop'. To
enable this
> you must right click on My Computer and choose properties. Then choose
the
> Remote Desktop tab and remove the tick from the Remote Desktop option
> (normally found as the second of the two option on the tab). I'm using
WinXP
> as the TS client to connect to Win2K servers this way and it works
without
> problems. 

Removed the checkbox, logged on with an Admin account and then and User
account, but both times still saw the "The client could not connect. You
are already connected to the console of this computer..." message.


> For some reason (can't quite remember why) I also chose to use
127.0.0.2 as
> the localhost connection. In case you can't get it to work after
disabling
> Remote Desktop, please try to switch to 127.0.0.2. That might just do
the

Haven't tried that, but as neither the 127.0.0.1 nor the 10.0.0.x
addresses work, I doubt any other IP that can similarly be resolved back
to the same machine would work.


Thanks if anyone can help.


-- 
Aidan Whitehall <mailto:[email protected]>
Macromedia ColdFusion Developer
Fairbanks Environmental Ltd  +44 (0)1695 51775
Queen's Awards Winner 2003 <http://www.fairbanks.co.uk/go/awards>

Fairbanks uses anti-spam filtering. If you sent an e-mail and expected
to receive a response but didn't, please call -- it may be that your
e-mail didn't make it to the intended mailbox.

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn