Remote desktop?

Reza86 · 9 Nov 2009 at 14:33

Ok so I'm trying to use remote desktop between 2 computers running Windows 7 ultimate, at home it will work fine if I just pop in the local IP of the computer I want to connect to eg 192.168.1.90. What would I need to put in to connect to the same computer from say university?

iNPUt · 9 Nov 2009 at 14:46

The home computers external IP, if it is a dynamic ip would get a no-ip.com, then you will have to make sure the computer / port (3389) is acessable from the external ip via the router.

Also might be worth checking if at Uni they allow those sort of external connections, mine does but..

Reza86 · 9 Nov 2009 at 14:50

Yeah I'm studying computer forensics so have access to a un-moderated lab so no problems their.

My IP is dynamic but I get O2 Pro BB so can request a static one. Have set up Microsoft Remote Desktop as an application on the router so it should be forwarding the correct ports.

So when i type in say my static IP would it just be the IP of the router or the router:computer ip?

paradigm · 9 Nov 2009 at 15:03

I guess networks aren't included as part of your base course then

You need to put in your external facing IP address, so that'll be the one bound to your routers WAN port. Once the RDP traffic hits your router, the NAT policy you implemented will tell the outside world where to connect 3389 to.

Personally I wouldn't use 3389, I'd use a random external port, NAT'd to 3389 on the inside, just that bit more secure than leaving 3389 open, people are less likely to probe a random port number for RDP access.

in which case you'd connect with 10.10.10.10:9283 (where 10.10.10.10 is your external IP and 9283 is the port you forwarded to 3389 on the router).

Reza86 · 9 Nov 2009 at 15:09

I've just started studying it his year, not covered this yet though. Thanks for the help I'll try that.

AbsenceJam · 9 Nov 2009 at 15:22

I would suggest also or alternatively using logmein. Works though NAT, no IP worries and browser based. I still use RDP as it's nicer to use but logmein is ever so handy as a backup or when I can't use RDP.

Reza86 · 9 Nov 2009 at 15:31

Ok cool will use that as a backup.

bigredshark · 9 Nov 2009 at 16:24

paradigm said:
I guess networks aren't included as part of your base course then

You need to put in your external facing IP address, so that'll be the one bound to your routers WAN port. Once the RDP traffic hits your router, the NAT policy you implemented will tell the outside world where to connect 3389 to.

Personally I wouldn't use 3389, I'd use a random external port, NAT'd to 3389 on the inside, just that bit more secure than leaving 3389 open, people are less likely to probe a random port number for RDP access.

in which case you'd connect with 10.10.10.10:9283 (where 10.10.10.10 is your external IP and 9283 is the port you forwarded to 3389 on the router).

Each to their own, but I very strongly disagree with this. Security through obscurity doesn't work, gives a false sense of security and is bad practice in my opinion and I discourage it at every possible opportunity.

EDIT: I should expand, personally I think leaving RDP open to the internet on any port is pretty much asking for trouble. Either lock it down to specific external IPs or use a VPN.

paradigm · 9 Nov 2009 at 17:29

bigredshark said:
Each to their own, but I very strongly disagree with this. Security through obscurity doesn't work, gives a false sense of security and is bad practice in my opinion and I discourage it at every possible opportunity.

EDIT: I should expand, personally I think leaving RDP open to the internet on any port is pretty much asking for trouble. Either lock it down to specific external IPs or use a VPN.

Well yes, personally I have RDP open (on an obscure port) to only 3 IP's, work, a friends, and a relatives house. Everything else comes in via my VPN.

But not knowing what kit he has, it would be daft of me to suggest things that may or may not be possible.

Reza86 · 9 Nov 2009 at 22:25

bigredshark said:
Each to their own, but I very strongly disagree with this. Security through obscurity doesn't work, gives a false sense of security and is bad practice in my opinion and I discourage it at every possible opportunity.

EDIT: I should expand, personally I think leaving RDP open to the internet on any port is pretty much asking for trouble. Either lock it down to specific external IPs or use a VPN.

Ok well how could I restrict RDC to specific IP addresses?