From: The Rev [MCT] on
Yeah - I've done 5 RDP Sessions - one inside another before.

I had an issue with some routers an data flow so we were unable to push past
3 routers form out side the network, but I was able to push inside from one
hop to another one at a time. So to get to the problem router I had to RDP
into each subnet from inside the last RDP. After which I was able to hit the
routers remote console.

Terminal Services is a lot of fun. :-)

--
..rev - mct.mcngp.44
..
"It is the mark of an educated man to be able to entertain a thought without
accepting it"
~Aristotle.
..
"LRM" <Fskspam(a)friedspam.com> wrote in message
news:ueulLUMwGHA.1436(a)TK2MSFTNGP02.phx.gbl...
> "Cheri Holloway" <meanju2REMOVETHIS(a)aol.com> wrote in message
> news:uMb3DIMwGHA.2036(a)TK2MSFTNGP05.phx.gbl...
>> Ok, here's my scenerio. I am studying for my MCDST and came across remote
>> desktop configuration and decided to play around with my own network
>> using port forwarding on my router. I sucessfully forwarded all incoming
>> connections to port 3389 to my server (running Exchange Server 2003) and
>> was able to connect sucessfully from inside and outside my local network.
>> But here is what I want to do. I want to ALSO set up a connection to my
>> desktop computer running XP Pro. Because I can only forward port 3389 to
>> one computer, I was wondering how I can configure another connection to
>> forward to the other computer. I researched microsoft's knowledge base
>> and found out I can use the 255.255.255.255:1234 (IP being the IP of the
>> network and the port being the configured port) to connect remotely using
>> a different port, so I configured my router to forward 3390 to my
>> desktop, enabled remote desktop on the my desktop, opened the port on my
>> firewall, and tested it. It didn't work. I am able to remote to the
>> desktop from INSIDE the network, but not from outside. What can I do?
>>
> Which kb are you referencing? I don't bother with setting up a second
> forwarder. When I login to the first box I can create as many rdp
> connections to my internal network as I like.
>
> --
> LRM
> MCNGP 7^2
> www.mcngp.com home of the bogosity singularity.
>

From: Consultant on
double true

"FrisbeeĀ" <billLASTNAME(a)yahoo.com> wrote in message
news:%23PqwijSwGHA.4872(a)TK2MSFTNGP02.phx.gbl...
> "Cheri Holloway" <meanju2REMOVETHIS(a)aol.com> wrote in message
> news:uMb3DIMwGHA.2036(a)TK2MSFTNGP05.phx.gbl...
>> Ok, here's my scenerio. I am studying for my MCDST and came across remote
>> desktop configuration and decided to play around with my own network
>> using port forwarding on my router. I sucessfully forwarded all incoming
>> connections to port 3389 to my server (running Exchange Server 2003) and
>> was able to connect sucessfully from inside and outside my local network.
>> But here is what I want to do. I want to ALSO set up a connection to my
>> desktop computer running XP Pro. Because I can only forward port 3389 to
>> one computer, I was wondering how I can configure another connection to
>> forward to the other computer. I researched microsoft's knowledge base
>> and found out I can use the 255.255.255.255:1234 (IP being the IP of the
>> network and the port being the configured port) to connect remotely using
>> a different port, so I configured my router to forward 3390 to my
>> desktop, enabled remote desktop on the my desktop, opened the port on my
>> firewall, and tested it. It didn't work. I am able to remote to the
>> desktop from INSIDE the network, but not from outside. What can I do?
>
> R U Hawt?
>


From: gremln007 on

Dragon Without Wings wrote:
> "Jonathan Roberts" wrote:
>
> > You missed one step. You need to configure RDP on the XP box to use the
> > revised port#.
> >
> >
>
> True. By default, RDP on the XP box only listen to port 3389. What you can
> do is to modify the RDP file. You can create an RDP connection file using a
> text editor. The simplest way to do it initially, though, is to run the
> mstsc client, configure basic settings you want, then choose "Save As..." on
> the General tab. You can then open the resulting file in Notepad and work
> with it. From there, you can change the server port to suite your need.
> Neat huh ?

Unless I mis-understand you, you would still need to modify the
listening port.

From: gremln007 on

Dragon Without Wings wrote:
> "Jonathan Roberts" wrote:
>
> > You missed one step. You need to configure RDP on the XP box to use the
> > revised port#.
> >
> >
>
> True. By default, RDP on the XP box only listen to port 3389. What you can
> do is to modify the RDP file. You can create an RDP connection file using a
> text editor. The simplest way to do it initially, though, is to run the
> mstsc client, configure basic settings you want, then choose "Save As..." on
> the General tab. You can then open the resulting file in Notepad and work
> with it. From there, you can change the server port to suite your need.
> Neat huh ?

Unless I mis-understand you, you would still need to modify the
listening port.

From: Briscobar on

"Cheri Holloway" <meanju2REMOVETHIS(a)aol.com> wrote in message
news:uMb3DIMwGHA.2036(a)TK2MSFTNGP05.phx.gbl...
> Ok, here's my scenerio. I am studying for my MCDST and came across remote
> desktop configuration and decided to play around with my own network using
> port forwarding on my router. I sucessfully forwarded all incoming
> connections to port 3389 to my server (running Exchange Server 2003) and
> was able to connect sucessfully from inside and outside my local network.
> But here is what I want to do. I want to ALSO set up a connection to my
> desktop computer running XP Pro. Because I can only forward port 3389 to
> one computer, I was wondering how I can configure another connection to
> forward to the other computer. I researched microsoft's knowledge base and
> found out I can use the 255.255.255.255:1234 (IP being the IP of the
> network and the port being the configured port) to connect remotely using
> a different port, so I configured my router to forward 3390 to my desktop,
> enabled remote desktop on the my desktop, opened the port on my firewall,
> and tested it. It didn't work. I am able to remote to the desktop from
> INSIDE the network, but not from outside. What can I do?

I don't have the exact key handy, but you'll have to edit the registry to
get RDP to listen to a different port. IIRC it's 2 keys' values you'll have
to change. Or, alternatively, and this is what I frequently do, is set up a
RD to one machine, then on that machine, set up more RD's to other machines.
This way, when I'm outside my network, I can remote into my network, then
hop nimbly-bimbly from machine to machine via other RD's.

HTH.