RDC to computer behind router

How do I connect to a computer behind a router and part of a network?

My setup is...
Gateway: 65.65.200.150 (fake)
Server: 65.65.200.151 (fake)
Router: 192.168.10.1
Server: 192.168.10.5
Computer to connect to: 192.168.10.50

I set the router to forward: RDC - 4545 to 4545 - 192.168.10.5 (main server)

RDC setup as...
Computer: COMP1 (also tried 192.168.10.50)
Username: billie
Password: secret
Domain: 65.65.200.151 (also tried 65.65.200.151:4545)

All I get is can't be found.

Thanks!

"shank" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> How do I connect to a computer behind a router and part of a network?
>
> My setup is...
> Gateway: 65.65.200.150 (fake)
> Server: 65.65.200.151 (fake)
> Router: 192.168.10.1
> Server: 192.168.10.5
> Computer to connect to: 192.168.10.50
>
> I set the router to forward: RDC - 4545 to 4545 - 192.168.10.5 (main server)
>
> RDC setup as...
> Computer: COMP1 (also tried 192.168.10.50)
> Username: billie
> Password: secret
> Domain: 65.65.200.151 (also tried 65.65.200.151:4545)
>
> All I get is can't be found.
>
> Thanks!
>
>


Hello again, Shank!

Actually it's referred to as RDP (Remote Desktop Protocol) where you will be using an RDC (remote desktop connection) to connect to it.

RDP uses TCP 3389, not 4545, unless you are using some other means to connect. SBS (Small Business Server) uses RWW (Remote Web Workplace), which is port 4125.

If you are using RDP, on the NAT device you would port remap 3389 to 192.168.10.50.

To connect to it from the outside world, open Remote Desktop Connection, or if on a server, open Remote Desktops, and connect to the WAN IP. The NAT device will send the traffic to the inside IP that you remapped it to. The computer you are connecting to will come up with the regular Windows logon box where you would log on normally as if you were on the machine.

If you are connecting to it from within the network (not from the outside world), or using a VPN (once it is connected), then you would connect to the internal private IP, and logon as if you were on the machine itself.

If you set the port remap to the server, 192.168.10.5, then the connection will go to that machine, not to the other computer at 192.168.10.150. To get to that machine from the outside world, you would first connect to 192.168.10.5, then after logging on to the server, you would then open an RDP session while logged on to the server to connect to the other computer.

RDP does not have a 'proxying' capability as some third party remote tools do, such as VNC, RADMIN, etc, where you can connect to the application on one machine with it running on it, then it will ask you to choose another computer from a list. However, SBS' RWW you can.


Suggestion about the fake IPs you've been posting:
For future posts, I would recommend to not pick a fake IP at random, such as the ones you have been using, unless they are actually yours. The ones you've been posting are actually live IPs that belong to someone out there, and posting them in a public forum without their knowledge or permission may give some folks that are not so honest, ideas to attack them, and they won't even know what's going on. You can post your own, or just post them as "WAN IP: x.x.x.x" or "WAN IP: 65.x.x.x."

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay

"Ace Fekay [Microsoft Certified Trainer]" <(E-Mail Removed)>
wrote in message news:%(E-Mail Removed)...
"shank" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> How do I connect to a computer behind a router and part of a network?
>
> My setup is...
> Gateway: 65.65.200.150 (fake)
> Server: 65.65.200.151 (fake)
> Router: 192.168.10.1
> Server: 192.168.10.5
> Computer to connect to: 192.168.10.50
>
> I set the router to forward: RDC - 4545 to 4545 - 192.168.10.5 (main
> server)
>
> RDC setup as...
> Computer: COMP1 (also tried 192.168.10.50)
> Username: billie
> Password: secret
> Domain: 65.65.200.151 (also tried 65.65.200.151:4545)
>
> All I get is can't be found.
>
> Thanks!
>
>


Hello again, Shank!

Actually it's referred to as RDP (Remote Desktop Protocol) where you will be
using an RDC (remote desktop connection) to connect to it.

RDP uses TCP 3389, not 4545, unless you are using some other means to
connect. SBS (Small Business Server) uses RWW (Remote Web Workplace), which
is port 4125.

If you are using RDP, on the NAT device you would port remap 3389 to
192.168.10.50.

To connect to it from the outside world, open Remote Desktop Connection, or
if on a server, open Remote Desktops, and connect to the WAN IP. The NAT
device will send the traffic to the inside IP that you remapped it to. The
computer you are connecting to will come up with the regular Windows logon
box where you would log on normally as if you were on the machine.

If you are connecting to it from within the network (not from the outside
world), or using a VPN (once it is connected), then you would connect to the
internal private IP, and logon as if you were on the machine itself.

If you set the port remap to the server, 192.168.10.5, then the connection
will go to that machine, not to the other computer at 192.168.10.150. To get
to that machine from the outside world, you would first connect to
192.168.10.5, then after logging on to the server, you would then open an
RDP session while logged on to the server to connect to the other computer.

RDP does not have a 'proxying' capability as some third party remote tools
do, such as VNC, RADMIN, etc, where you can connect to the application on
one machine with it running on it, then it will ask you to choose another
computer from a list. However, SBS' RWW you can.


Suggestion about the fake IPs you've been posting:
For future posts, I would recommend to not pick a fake IP at random, such as
the ones you have been using, unless they are actually yours. The ones
you've been posting are actually live IPs that belong to someone out there,
and posting them in a public forum without their knowledge or permission may
give some folks that are not so honest, ideas to attack them, and they won't
even know what's going on. You can post your own, or just post them as "WAN
IP: x.x.x.x" or "WAN IP: 65.x.x.x."

--
Ace
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
I just got another chance to look at this...
>>If you are using RDP, on the NAT device you would port remap 3389 to
>>192.168.10.50<<

It seems if I do that, then the only station I could use with RDC is the one
defined in routing. Assuming multiple computers on a network that get their
local IP dynamically, how would you instruct the server to re-route incoming
RDC to the computer name?
thanks!

"shank" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> I just got another chance to look at this...
>>>If you are using RDP, on the NAT device you would port remap 3389 to
>>>192.168.10.50<<
>
> It seems if I do that, then the only station I could use with RDC is the one
> defined in routing. Assuming multiple computers on a network that get their
> local IP dynamically, how would you instruct the server to re-route incoming
> RDC to the computer name?
> thanks!
>
>

That is right.You can only port remap one IP per port in a NAT. You can't instruct it to proxy the request to another. You would simply RDP (once again, it's not called RDC), into the server, then when logged on the server, open another RDP connection to the internal machine you need to get to.

If this is for multiple users to get in, then you will need to look at a third party product.

Ace

Hello,

You can go tricky, and ask the router to do :

3389 -> server (3389)
3390 -> workstation 1 (3389)
3391 -> workstation 2 (3389)

If your router can't change destination port on the fly, then you can change
RDP port your workstation listen to:
How to change the listening port for Remote Desktop
http://support.microsoft.com/?scid=k...06759&x=9&y=17

You can also change your solution, and use for example logmein services.
This is a real different technical solution, but works great.
The free edition doesn't have limit i am aware of in the number of computer
managed.
Computers have an agent, and send the desktop screen to a logmein server
using https. Then you, from outside, connect to logmein servers to get the
display.


Cordialement,
Mathieu Chateau
fr blog: http://www.lotp.fr
en blog: http://lordoftheping.blogspot.com


A> "shank" <(E-Mail Removed)> wrote in message
A> news:(E-Mail Removed)...
A>
>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- I just
>> got another chance to look at this...
>>
>>>> If you are using RDP, on the NAT device you would port remap 3389
>>>> to 192.168.10.50<<
>>>>
>> It seems if I do that, then the only station I could use with RDC is
>> the one
>> defined in routing. Assuming multiple computers on a network that get
>> their
>> local IP dynamically, how would you instruct the server to re-route
>> incoming
>> RDC to the computer name?
>> thanks!
A> That is right.You can only port remap one IP per port in a NAT. You
A> can't instruct it to proxy the request to another. You would simply
A> RDP (once again, it's not called RDC), into the server, then when
A> logged on the server, open another RDP connection to the internal
A> machine you need to get to.
A>
A> If this is for multiple users to get in, then you will need to look
A> at a third party product.
A>
A> Ace
A>