REmote Desktop via localhost to s specified port

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Yelp, this works fine on 2k and older win versions. XP
declares"you already have a console connection"

I'm doing port redirection so my RDP connection is declared
by Localhost rather than the name or IP of the Terminal server.
In XP however, just stating localhost immediately generates
the err, the desktop enver even tries to look outside of my
local machine.

This works fine on older windows versions and is placing a
whole consulting job in jepoardy if I can't get WinXP to
connect via RDP to a "localhose😛ort#" address same as the
older versions do.
Yelp.
Thanks in advance, I've gott believe someone else has seen
this before nad has found a solution.
Sincerely to all,
Barry

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

"Barry Burr" <jkerouac@speakeasy.net> wrote in message news:<47ee01c4735b$f42ca040$a401280a@phx.gbl>...
> Yelp, this works fine on 2k and older win versions. XP
> declares"you already have a console connection"
>
> I'm doing port redirection so my RDP connection is declared
> by Localhost rather than the name or IP of the Terminal server.
> In XP however, just stating localhost immediately generates
> the err, the desktop enver even tries to look outside of my
> local machine.

Try connecting to 127.0.0.2 - the forwarding program may be
listening on that address too.

Alternately, you can run the RDP client in 2000 compatibility
mode to get the old behaviour.

Hth,
Ian

 

[Chad]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

ian.mcgowan@gmail.com (Ian McGowan) wrote in message news:<c75d39ff.0407301847.50d3020f@posting.google.com>...
> "Barry Burr" <jkerouac@speakeasy.net> wrote in message news:<47ee01c4735b$f42ca040$a401280a@phx.gbl>...
> > Yelp, this works fine on 2k and older win versions. XP
> > declares"you already have a console connection"
> >
> > I'm doing port redirection so my RDP connection is declared
> > by Localhost rather than the name or IP of the Terminal server.
> > In XP however, just stating localhost immediately generates
> > the err, the desktop enver even tries to look outside of my
> > local machine.
>
> Try connecting to 127.0.0.2 - the forwarding program may be
> listening on that address too.
>
> Alternately, you can run the RDP client in 2000 compatibility
> mode to get the old behaviour.
>
> Hth,
> Ian


Windows XP SP2 breaks alternate localhost addresses such as 127.0.0.2.

 

[Chad]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

chad@bluestream.org wrote in message news:<99ab3348.0408121841.217487d@posting.google.com>...
> ian.mcgowan@gmail.com (Ian McGowan) wrote in message news:<c75d39ff.0407301847.50d3020f@posting.google.com>...
> > "Barry Burr" <jkerouac@speakeasy.net> wrote in message news:<47ee01c4735b$f42ca040$a401280a@phx.gbl>...
> > > Yelp, this works fine on 2k and older win versions. XP
> > > declares"you already have a console connection"
> > >
> > > I'm doing port redirection so my RDP connection is declared
> > > by Localhost rather than the name or IP of the Terminal server.
> > > In XP however, just stating localhost immediately generates
> > > the err, the desktop enver even tries to look outside of my
> > > local machine.
> >
> > Try connecting to 127.0.0.2 - the forwarding program may be
> > listening on that address too.
> >
> > Alternately, you can run the RDP client in 2000 compatibility
> > mode to get the old behaviour.
> >
> > Hth,
> > Ian
>
>
> Windows XP SP2 breaks alternate localhost addresses such as 127.0.0.2.

"Good" news in that Microsoft is releasing a fix. See this post for
more details:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=ONu5EZogEHA.384%40TK2MSFTNGP10.phx.gbl

Chad
http://www.wissh.com