Remote Desktop from outside network

[latrosicarius]

Hello, I would like to be able to connect to computers on my network from outside the network with Remote Desktop...

I know how to do it with port forwarding my router to the specific PC I want to connect to. However, I want the ability to connect to any PC on the network from OFF the network so long as I log in with their appropriate user names & passwords and their computer is ON.

The way I was thinking of doing this is port forwarding the router, not to a PC, but to the server. Then, I would actually be connecting to the server from the offsite location, which would somehow redirect me to the appropriate PC I want to log into.

Is this possible?

Thanks!

[Moby-Dick]

you can next RDP sessions if you want
in fact windows SBS 2003 does somethign like that seemlesly and allows you to remote desktop any client machine from outside the network.

[latrosicarius]

Hey Moby, that sounds like great news for me, but I don't understand what you mean by next RDP sessions

Do you have any more info on it?

thanks for the reply tho!

[Moby-Dick]

doh ....I ment nest

ie rdp into server A
and from there to server b

[explicitlyrics]

Just a hint, if you enable RDC to your server from any location on the internet then ALL users will need secure passwords, not just yours. Also if you use WinXP Pro then go to control panel, click administrative tools, then local security policy. Then click account policies and then account lockout policies. Here you can set it such that if you log in with a bad username and password it stops you logging in again for a configurable amount of time. Its not amazingly useful, but does help to add a little security to your PC....

[latrosicarius]

Cool thanks I will try to look up nesting rdp stuff, and about the passwords, everyone already has their own secure passwords b/c we are on a domain, but I didn't know about that timed delay thing. That sounds good!

ty

[latrosicarius]

Should I install the Terminal Server role or something like that on the Win 2003 Server machine?

Also, when I Remote Desktop into the server, and then from there, Remote Desktop into the client PC, is it smart enough to "redirect" the Remote Desktop connection, or does it waste efficiency by having to go through the client AND the server?

Also, this seems like a workable solution, but it doesn't seem like it would work in a real office situation where you don't trust people to Remote Desktop themselves into the server...

How do real companies allow people to connect to their computers while they are on the road?

Thanks!

[arthurleung]

Should I install the Terminal Server role or something like that on the Win 2003 Server machine?

Also, when I Remote Desktop into the server, and then from there, Remote Desktop into the client PC, is it smart enough to "redirect" the Remote Desktop connection, or does it waste efficiency by having to go through the client AND the server?

Also, this seems like a workable solution, but it doesn't seem like it would work in a real office situation where you don't trust people to Remote Desktop themselves into the server...

How do real companies allow people to connect to their computers while they are on the road?

Thanks!

Set a NAT rule on your server, redirect something like port 10000 to port 3389 of the destination machine, then you connect to serverip:10000 in remote desktop to access your machine

Good for situation like you got 10 computers and you want RDP to all of them, just point from 10000~10009 to 3389 of each machine (i.e. 10000 to machine 1, 10001 to machine 2, etc) and everyone can have a rdp port for themselves.

[Moby-Dick]

Should I install the Terminal Server role or something like that on the Win 2003 Server machine?

Also, when I Remote Desktop into the server, and then from there, Remote Desktop into the client PC, is it smart enough to "redirect" the Remote Desktop connection, or does it waste efficiency by having to go through the client AND the server?

Also, this seems like a workable solution, but it doesn't seem like it would work in a real office situation where you don't trust people to Remote Desktop themselves into the server...

How do real companies allow people to connect to their computers while they are on the road?

Thanks!

- The terminal server role is for application mode terminal services - you would only be using remote control , which you enable from the properties of my computer.

-No it wont dynamically redirect the connection, Yes it is a bit slower

- Real World ? As I say you would use the Remote Web Workspace feature if you have SBS2003 set up correctly.

-Real (small ) companies might use Remote Web Workspace , or Add a few extra PAT routes to connect to multiple boxes from a single external IP.

- Larger companies would be less likely to give their road warriors remote desktop access , more likely a laptop and VPN. Dont forget things like outlook web access can elinimate the need for either at times.

[Moby-Dick]

Set a NAT rule on your server, redirect something like port 10000 to port 3389 of the destination machine, then you connect to serverip:10000 in remote desktop to access your machine

Good for situation like you got 10 computers and you want RDP to all of them, just point from 10000~10009 to 3389 of each machine (i.e. 10000 to machine 1, 10001 to machine 2, etc) and everyone can have a rdp port for themselves.

this is the PAT I mentioned ( Port Address Translation ) FWIW I used to use 3389x as the port where x was for the specific machine

[latrosicarius]

this is the PAT I mentioned ( Port Address Translation ) FWIW I used to use 3389x as the port where x was for the specific machine

Hi Moby, I can do this port forwarding thing on the router, but how would I set it up on the server like you suggest? Thanks

[oclocker]

hamachi !

[latrosicarius]

That program looks pretty cool, but I want to try to set it up first without having to install any software.

I have a problem port forwarding on my router. I can't set up port forwarding for multiple computers to 3389 b/c it only accepts 3389 in the list once.

For instance, I tried:
RDP 101
public port 10101
private port 3389
IP 196.168.0.101

This works, but it won't let me add another one for another computer:

RDP 102
public port 10102
private port 3389
IP 196.168.0.102

So, if my router can't do it, can it be done via the server some how? At this point, i have no other way of doing it besides nesting, which I don't want to have to do unless necessary b/c it would mean I have to let the other ppl know the server's password

Can anyone help please? Thanks

[Paul Adams]

I have a problem port forwarding on my router. I can't set up port forwarding for multiple computers to 3389 b/c it only accepts 3389 in the list once.

For instance, I tried:
RDP 101
public port 10101
private port 3389
IP 196.168.0.101

This works, but it won't let me add another one for another computer:

RDP 102
public port 10102
private port 3389
IP 196.168.0.102

The router won't let you add 2 unique rules as above?
That's a bit poor, and sounds like a fundamental bug with the firmware or UI - what is the make/model & firmware revision of the router?

So long as the public port and private port or private IP are a unique then it should be a valid forwarding rule.

[latrosicarius]

Yes, that's what I thought. I don't think it should be a problem, but it's never as easy as it should be lol.

My router is the D-Link DGL-4100 GamerLounge Broadband Gigabit Gaming Router.

Firmware is 1.0, but 1.6 is available. I'll try it and let you know.

[latrosicarius]

Actually, the v1.6 firmware fixed it!! Sorry for the trouble. Thanks a lot!