Remote Desktop to home server

[ToiletDuck]

While I'm in the process of updating my home server I wanted to ask how I could remote desktop to it. It's currently on ATT Uverse so it's not the only computer behind their router.

I've never tried this so what steps should I go through?

[bchur83]

I would say your best bet is to use Logmein. It doesnt require any router configuration, it's free, and it is easy to setup. I use it on many of my machines.

[thideras]

You could always forward the port for the router, but then it opens the server to attack. Instead of RDP for an external network, I'd suggest using LogMeIn (or a similar program). No port forwarding is needed and setup is quick.

[ToiletDuck]

Thanks guys had never heard of that one!

[PeddlerOfFlesh]

If your router lets you, you could also forward a non-standard port to the RDP port, which would make it less likely to be scanned. If it is scanned and they're using some kind of service discovery they will see it is RDP. However, if that is the only port you have open to the outside world, they're pretty much limited to a brute force attack and you can easily set it to lock out after x number of failed attempts. If an exploit were to come along for RDP then you could have problems too.

I'm not sure about what OS your using, but if it allows multiple logons, LogMeIn just takes you to the user that is logged onto the console. I actually don't remember why, but I tend to stick to RDP. For a while I was using RDP over LAN and LogMeIn over the internet (LogMeIn will use the internet even if you are on a LAN) but decided to use RDP instead. Now I'm starting to wonder why... I'm pretty sure LogMeIn uses less bandwidth too.

[thideras]

I'm not sure about what OS your using, but if it allows multiple logons, LogMeIn just takes you to the user that is logged onto the console.This is incorrect. You specify the login credentials when you connect, so you can log in as any user.

[DaveHCYJ]

If your router lets you, you could also forward a non-standard port to the RDP port, which would make it less likely to be scanned. If it is scanned and they're using some kind of service discovery they will see it is RDP. However, if that is the only port you have open to the outside world, they're pretty much limited to a brute force attack and you can easily set it to lock out after x number of failed attempts. If an exploit were to come along for RDP then you could have problems too.

Historically RDP has been pretty secure and its a major pain to brute force compared to some other services. So using a non standard port isn't a bad solution.

I would probably use an ssh tunnel or vpn sort of solution and run RDP through that, but that adds another layer of complexity you may not want to setup. Thats just me though, since I don't know anything about LogMeIn. Perhaps if you're looking for the easiest solution you might try LogMeIn as others suggested.

[PeddlerOfFlesh]

This is incorrect. You specify the login credentials when you connect, so you can log in as any user.

Interesting. You are correct. When I used it a while ago (maybe a year or more) it only asked me for a computer password after logging into the site and choosing the computer for remote desktop, then gave me the user that was logged in at the console. I had left it installed and even installed updates to it when prompted, so I decided to try it again now that you mentioned it and it does indeed ask for a username.

Historically RDP has been pretty secure and its a major pain to brute force compared to some other services. So using a non standard port isn't a bad solution.

I would probably use an ssh tunnel or vpn sort of solution and run RDP through that, but that adds another layer of complexity you may not want to setup. Thats just me though, since I don't know anything about LogMeIn. Perhaps if you're looking for the easiest solution you might try LogMeIn as others suggested.

I have known people that swear by VNC, yet every implementation of it that I have seen is crap. It's slow, disconnects easily and is pretty lacking in features. LogMeIn basically acts like a VPN with NAT traversal with a desktop sharing app built in.

TeamViewer is another thing you can look into. It's similar to LogMeIn. Based on my limited experience with it I would prefer LogMeIn over it.

RDP also has the advantage of have a large amount of computers with it's client already installed. This would be of benefit if you plan on getting into your computer from a client computer that you don't have admin access to.