RDP remotely - Multiple servers

How do most people do this?
I need to be able to RDP in multiple servers. The servers here are already
setup to do that: someone edited the registry on servers to configure RPD to
listen on a different port than 3389.

But what I don't like is; since some of the servers have been changed to
listen on a port other than the default, when I'm on the LAN, I have to use
the external ip address and the port number. I can't just put
ServerNameortNumber
I have to put ExternalIPaddressortNumber

Is that normal? That I can't use the host name when using RDP locally?

"JohnB" <> wrote in message
news:%...
> How do most people do this?
> I need to be able to RDP in multiple servers. The servers here are
> already setup to do that: someone edited the registry on servers to
> configure RPD to listen on a different port than 3389.
>
> But what I don't like is; since some of the servers have been changed to
> listen on a port other than the default, when I'm on the LAN, I have to
> use the external ip address and the port number. I can't just put
> ServerNameortNumber
> I have to put ExternalIPaddressortNumber
>
> Is that normal? That I can't use the host name when using RDP locally?

If your servers are all on the internal network, without any routers in
between, then you can reach each of them with this command:

mstsc /v:ServerName:PortNumber or
mstsc /v:IPAddress:PortNumber

In article <#>,
says...
>
> How do most people do this?
> I need to be able to RDP in multiple servers. The servers here are already
> setup to do that: someone edited the registry on servers to configure RPD to
> listen on a different port than 3389.
>
> But what I don't like is; since some of the servers have been changed to
> listen on a port other than the default, when I'm on the LAN, I have to use
> the external ip address and the port number. I can't just put
> ServerNameortNumber
> I have to put ExternalIPaddressortNumber
>
> Is that normal? That I can't use the host name when using RDP locally?

Your firewall should allow you to map any TCP port to another Port - as
an example, I use TCP 59000 external mapped to 3389 Internal from the
external IP, for server 0, then 59001 to 3389 for server 1, this means I
don't have to change the RDP port on the LAN side at all, and I can use
a SINGLE public IP to reach the internal servers, in fact, since I'm
using a different external Port I can connect to multiple servers at the
same time.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)

Worked great.
Learned something new; the "v" switch.
Thanks.



"Pegasus [MVP]" <> wrote in message
news:%...
>
> "JohnB" <> wrote in message
> news:%...
>> How do most people do this?
>> I need to be able to RDP in multiple servers. The servers here are
>> already setup to do that: someone edited the registry on servers to
>> configure RPD to listen on a different port than 3389.
>>
>> But what I don't like is; since some of the servers have been changed to
>> listen on a port other than the default, when I'm on the LAN, I have to
>> use the external ip address and the port number. I can't just put
>> ServerNameortNumber
>> I have to put ExternalIPaddressortNumber
>>
>> Is that normal? That I can't use the host name when using RDP locally?
>
> If your servers are all on the internal network, without any routers in
> between, then you can reach each of them with this command:
>
> mstsc /v:ServerName:PortNumber or
> mstsc /v:IPAddress:PortNumber
>

"JohnB" <> wrote in message
news:...
> Worked great.
> Learned something new; the "v" switch.
> Thanks.

It pays to nose about a bit, usually by typing the current command like so:

mstsc /?