Prev: The POP3 Service could not start bacause:
Next: 70-293 simulations
From: Briscobar on 21 Aug 2006 22:01

"Dragon Without Wings" <DragonDance(a)LordofTheRing.com> wrote in message
news:9CA800A5-C1DF-403D-BB63-42C5868E7B1A(a)microsoft.com...
> "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 ?

Huh. Learn somethin new every day. I didn't know RDP files were
text-editable. Sweet.


From: Briscobar on 21 Aug 2006 22:01

"Dragon Without Wings" <DragonDance(a)LordofTheRing.com> wrote in message
news:9CA800A5-C1DF-403D-BB63-42C5868E7B1A(a)microsoft.com...
> "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 ?

Huh. Learn somethin new every day. I didn't know RDP files were
text-editable. Sweet.


From: Simon Dobson on 24 Aug 2006 20:17
Briscobar wrote:
>
> 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.

The OP could always port forward say 3390 (WAN side) to 3389 on the LAN
side on a different machine. So:

ExternalIP:3389 --> Router:3389 --> PC1:3389
ExternalIP:3390 --> Router:3390 --> PC2:3389

Most routers can do this. Far better than buggering about with the
registry to change RDP's default port; avoid this as it means
remembering to specify a different port number internally too.
From: Simon Dobson on 24 Aug 2006 20:17
Briscobar wrote:
>
> 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.

The OP could always port forward say 3390 (WAN side) to 3389 on the LAN
side on a different machine. So:

ExternalIP:3389 --> Router:3389 --> PC1:3389
ExternalIP:3390 --> Router:3390 --> PC2:3389

Most routers can do this. Far better than buggering about with the
registry to change RDP's default port; avoid this as it means
remembering to specify a different port number internally too.
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: The POP3 Service could not start bacause:
Next: 70-293 simulations